Triple

T17321955
Position Surface form Disambiguated ID Type / Status
Subject Moses Austin E420581 entity
Predicate burialPlace P196 FINISHED
Object Potosi, Missouri 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: Potosi, Missouri | Statement: [Moses Austin, burialPlace, Potosi, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Potosi, Missouri
Context triple: [Moses Austin, burialPlace, Potosi, Missouri]
  • A. Potosi, Missouri chosen
    Potosi, Missouri is a small historic town in Washington County known for its early 19th-century lead mining industry and association with pioneer entrepreneur Moses Austin.
  • B. Montezuma, Missouri
    Montezuma, Missouri is a small unincorporated rural community located within Vernon County in the U.S. state of Missouri.
  • C. De Soto, Missouri
    De Soto, Missouri is a small city in eastern Missouri known historically as a railroad town and located within the St. Louis metropolitan area.
  • D. Bolivar, Missouri
    Bolivar, Missouri is a small city in Polk County that serves as the county seat and a regional hub in southwestern Missouri.
  • E. Taos, Missouri
    Taos, Missouri is a small incorporated community in central Missouri that forms part of the Jefferson City metropolitan area.
  • 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_69d889d22b848190a4663d0b8f8f76e7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e439d01e2c8190a358dace420d4575 completed April 19, 2026, 2:11 a.m.
Created at: April 10, 2026, 5:43 a.m.