Triple

T22940717
Position Surface form Disambiguated ID Type / Status
Subject Schubert, Missouri E569719 entity
Predicate hasName P744 FINISHED
Object Schubert, 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: Schubert, Missouri | Statement: [Schubert, Missouri, hasName, Schubert, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Schubert, Missouri
Context triple: [Schubert, Missouri, hasName, Schubert, Missouri]
  • A. Schubert, Missouri chosen
    Schubert, Missouri is a small unincorporated community located in Cole County in the central part of the state.
  • B. Sibley, Missouri
    Sibley, Missouri is a small village in western Missouri known for its proximity to the historic Fort Osage site along the Missouri River.
  • C. Estill, Missouri
    Estill, Missouri is a small unincorporated community located in Howard County in the central part of the state.
  • D. Seligman, Missouri
    Seligman, Missouri is a small rural city in southwestern Missouri near the Arkansas border, historically linked to the railroad and serving as a gateway to the Ozarks.
  • E. Van Buren, Missouri
    Van Buren, Missouri is a small town in the Ozarks that serves as a popular gateway for outdoor recreation along the Current and Jacks Fork rivers.
  • 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_69e24590862c8190858f180ad302adab completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1813844b88190b05d3829b0c423c4 completed April 29, 2026, 3:55 a.m.
Created at: April 17, 2026, 3:45 p.m.