Triple

T15505915
Position Surface form Disambiguated ID Type / Status
Subject DeKalb County, Missouri E379080 entity
Predicate hasCity P316 FINISHED
Object Osborn, Missouri E1067135 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: Osborn, Missouri | Statement: [DeKalb County, Missouri, hasCity, Osborn, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Osborn, Missouri
Context triple: [DeKalb County, Missouri, hasCity, Osborn, Missouri]
  • A. Osborn, Missouri chosen
    Osborn, Missouri is a small rural city in the Midwestern United States known for its agricultural surroundings and close-knit community.
  • B. Osceola, Missouri
    Osceola, Missouri is a small historic city in western Missouri known for its role in the Civil War and its location near Truman Lake.
  • C. Osage City, Missouri
    Osage City, Missouri is a small unincorporated community in central Missouri located within Cole County near the Missouri River.
  • D. Hopkins, Missouri
    Hopkins, Missouri is a small rural city located in Nodaway County in the northwest region of the state near the Iowa border.
  • E. 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.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fcd5d948190b25a67a72ef980e9 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69fff28d38a4819085bf051b566c17e7 completed May 10, 2026, 2:50 a.m.
Created at: April 10, 2026, 3:55 a.m.