Triple

T9917553
Position Surface form Disambiguated ID Type / Status
Subject Eastern Missouri E185907 entity
Predicate contains P35 FINISHED
Object Arnold, Missouri E782855 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: Arnold, Missouri | Statement: [Eastern Missouri, contains, Arnold, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Arnold, Missouri
Context triple: [Eastern Missouri, contains, Arnold, Missouri]
  • A. Arnold, Missouri chosen
    Arnold, Missouri is a suburban city in Jefferson County near St. Louis, known as a growing residential and commercial community in eastern Missouri.
  • B. Argyle, Missouri
    Argyle, Missouri is a small village in Maries and Osage counties known for its rural character within central Missouri.
  • C. Hopkins, Missouri
    Hopkins, Missouri is a small rural city located in Nodaway County in the northwest region of the state near the Iowa border.
  • D. Sheldon, Missouri
    Sheldon, Missouri is a small rural city located in southwestern Missouri within Vernon County.
  • E. New London, Missouri
    New London, Missouri is a small city in northeastern Missouri that serves as the administrative and governmental center of Ralls County.
  • 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_69ca829b45f481909040f7b99a1976ed completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cdb5673f108190914e0c172dddc65f completed April 2, 2026, 12:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d20dec42848190ab9f8663155df83f completed April 5, 2026, 7:23 a.m.
Created at: March 30, 2026, 8:42 p.m.