Triple

T6631107
Position Surface form Disambiguated ID Type / Status
Subject Georgia State Route 138 E149925 entity
Predicate connects P390 FINISHED
Object Fairburn, Georgia E77675 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: Fairburn, Georgia | Statement: [Georgia State Route 138, connects, Fairburn, Georgia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fairburn, Georgia
Context triple: [Georgia State Route 138, connects, Fairburn, Georgia]
  • A. Fairburn, Georgia chosen
    Fairburn, Georgia is a small city in the Atlanta metropolitan area known for its historic downtown and role as a growing suburban community.
  • B. Funston, Georgia
    Funston, Georgia is a small town located in Colquitt County in the southern part of the U.S. state of Georgia.
  • C. Bogart, Georgia
    Bogart, Georgia is a small town in northeastern Georgia located near the Athens metropolitan area.
  • D. Townsend, Georgia
    Townsend, Georgia is a small unincorporated community in coastal southeastern Georgia known for its rural character and proximity to marshlands and waterways.
  • E. Richwood, Georgia
    Richwood, Georgia is a small unincorporated rural community located in Dooly County in the U.S. state of Georgia.
  • 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_69c687ee50048190aa151765bef16193 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6afa6e52c8190943c86660da23c75 completed March 27, 2026, 4:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6e44f5f9c819088cfb4fd87887766 completed March 27, 2026, 8:10 p.m.
Created at: March 27, 2026, 1:59 p.m.