Triple

T14039952
Position Surface form Disambiguated ID Type / Status
Subject SR 100 (Georgia) E337817 entity
Predicate connects P390 FINISHED
Object Bowdon, Georgia E277511 NE FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Bowdon, Georgia | Statement: [SR 100 (Georgia), connects, Bowdon, Georgia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bowdon, Georgia
Context triple: [SR 100 (Georgia), connects, Bowdon, Georgia]
  • A. Bowdon, Georgia chosen
    Bowdon, Georgia is a small city in western Georgia known for its rural character and location near the Alabama state line.
  • B. Bogart, Georgia
    Bogart, Georgia is a small town in northeastern Georgia located near the Athens metropolitan area.
  • C. Fairburn, Georgia
    Fairburn, Georgia is a small city in the Atlanta metropolitan area known for its historic downtown and role as a growing suburban community.
  • D. Bullard, Georgia
    Bullard, Georgia is an unincorporated community located in Twiggs County in the central part of the U.S. state of Georgia.
  • E. Talbotton, Georgia
    Talbotton, Georgia is a small historic city in west-central Georgia known for its 19th-century architecture and role as the administrative and cultural center of Talbot County.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de30ee374081908b6b5e8f81dd90f2 completed April 14, 2026, 12:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc33dbc8c819080b6cb3d589da7a1 completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:20 p.m.