Triple

T22774791
Position Surface form Disambiguated ID Type / Status
Subject Pike County Courthouse E563664 entity
Predicate locatedIn P40 FINISHED
Object Zebulon, Georgia NE NERFINISHED

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: Zebulon, Georgia | Statement: [Pike County Courthouse, locatedIn, Zebulon, Georgia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zebulon, Georgia
Context triple: [Pike County Courthouse, locatedIn, Zebulon, Georgia]
  • A. Zebulon, Georgia chosen
    Zebulon, Georgia is a small historic city in central Georgia that serves as the administrative and cultural hub of Pike County.
  • B. Nahunta, Georgia
    Nahunta, Georgia is a small city in southeastern Georgia that serves as the county seat of Brantley County.
  • C. Tazewell, Georgia
    Tazewell, Georgia is a small unincorporated community in Marion County that historically served as a local county seat in west-central Georgia.
  • D. Buchanan, Georgia
    Buchanan, Georgia is a small city in northwestern Georgia that serves as the administrative and governmental center of Haralson County.
  • E. De Soto, Georgia
    De Soto, Georgia is a small rural city located in southwestern Georgia in the United States.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24554497c819080b996e071de27c2 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17b60eec48190b0aaf3eb7ede38d4 completed April 29, 2026, 3:30 a.m.
Created at: April 17, 2026, 3:28 p.m.