Skip to content

Write about the difference between GPT and Gemini in running our task #84

Description

@kctong529

Goal

Compare observed GPT and Gemini behavior in our route-navigation task.

Description

Write a project-specific comparison of GPT and Gemini based on actual dashboard/evaluation outputs.

The comparison should focus on practical behavior in our setup, not broad claims about the models in general.

Possible comparison points:

  • route validity
  • exact shortest-path match
  • JSON format reliability
  • tendency to hallucinate nodes or edges
  • ability to use SSAL graph context
  • sensitivity to prompt template changes
  • explanation quality
  • finish status / truncation behavior
  • consistency across similar prompts
  • common failure modes

Literature / background review

Include a small literature/background review on comparative LLM evaluation and model-to-model benchmarking.

The goal is to make the GPT/Gemini comparison methodologically careful.

The writeup should avoid broad claims such as “GPT is better at routing” unless supported by our data. Instead, it should frame the comparison as project-specific behavior under our route-navigation setup.

Useful angles:

  • comparative model evaluation
  • benchmark design and small-sample limitations
  • prompt sensitivity across models
  • output-format reliability
  • model behavior on reasoning or spatial tasks

Expected output:

  • 3–5 relevant sources
  • short note on how to compare models without overclaiming
  • report-ready limitation paragraph

Suggested work

  • Select representative evaluated runs from both providers.
  • Compare route validity and exact match results.
  • Compare JSON/schema reliability.
  • Compare common failure modes.
  • Include concrete examples where possible.
  • Avoid overgeneralizing beyond our small project dataset.
  • Write the comparison in final-report style.

Acceptance criteria

  • GPT/Gemini comparison is based on project outputs.
  • Differences are described with concrete examples where available.
  • The comparison includes route correctness and output-format behavior.
  • The comparison mentions limitations of sample size and prompt dependence.
  • The writeup avoids unsupported claims about the models in general.
  • Text is suitable for final report integration.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions