Triple

T13244875
Position Surface form Disambiguated ID Type / Status
Subject Corder, Missouri E315373 entity
Predicate hasAbbreviation P43 FINISHED
Object Corder, MO E315373 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: Corder, MO | Statement: [Corder, Missouri, hasAbbreviation, Corder, MO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corder, MO
Context triple: [Corder, Missouri, hasAbbreviation, Corder, MO]
  • A. Corder, Missouri chosen
    Corder, Missouri is a small city located in Lafayette County in the western part of the U.S. state of Missouri.
  • B. Steedman, Missouri
    Steedman, Missouri is a small unincorporated rural community located in Callaway County in the U.S. state of Missouri.
  • C. Rucker, Missouri
    Rucker, Missouri is an unincorporated rural community located in Randolph County in the U.S. state of Missouri.
  • D. Calhoun, Missouri
    Calhoun, Missouri is a small rural village located in Henry County in the west-central region of the state.
  • E. Horton, Missouri
    Horton, Missouri is a small unincorporated community located in Vernon County in the western part of the U.S. state of Missouri.
  • 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_69d806b1072881909e46bd212259c5f0 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d98d5b06148190a44e698bbe5cd529 completed April 10, 2026, 11:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6ff3600388190a7f61370f54d5e63 completed May 3, 2026, 7:54 a.m.
Created at: April 9, 2026, 9:23 p.m.