Triple

T22399211
Position Surface form Disambiguated ID Type / Status
Subject Richwood, Georgia E553713 entity
Predicate hasName P744 FINISHED
Object Richwood, 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: Richwood, Georgia | Statement: [Richwood, Georgia, hasName, Richwood, Georgia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richwood, Georgia
Context triple: [Richwood, Georgia, hasName, Richwood, Georgia]
  • A. Richwood, Georgia chosen
    Richwood, Georgia is a small unincorporated rural community located in Dooly County in the U.S. state of Georgia.
  • B. Richland, Georgia
    Richland, Georgia is a small city in Stewart County in southwestern Georgia, known historically as a rural community and regional crossroads.
  • C. Williamson, Georgia
    Williamson, Georgia is a small rural city located in Pike County in the west-central part of the U.S. state of Georgia.
  • D. Whigham, Georgia
    Whigham, Georgia is a small rural city in the southwestern part of the state known for its tight-knit community and agricultural surroundings.
  • E. Sylvania, Georgia
    Sylvania, Georgia is a small city in Screven County known as the county seat and a historic community in eastern Georgia.
  • 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_69e11e4da7048190b4387d422a9a0de5 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f158b28e58819090624f131ce63a9f completed April 29, 2026, 1:02 a.m.
Created at: April 16, 2026, 8:46 p.m.