Triple

T19305888
Position Surface form Disambiguated ID Type / Status
Subject Concordia, Kansas E482826 entity
Predicate namedAfter P63 FINISHED
Object Concordia, 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: Concordia, Missouri | Statement: [Concordia, Kansas, namedAfter, Concordia, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Concordia, Missouri
Context triple: [Concordia, Kansas, namedAfter, Concordia, Missouri]
  • A. Concordia, Missouri chosen
    Concordia, Missouri is a small city in western Missouri known for its agricultural roots and tight-knit rural community.
  • B. New London, Missouri
    New London, Missouri is a small city in northeastern Missouri that serves as the administrative and governmental center of Ralls County.
  • C. Conway, Missouri
    Conway, Missouri is a small rural city in the Ozarks region of south-central Missouri, known for its location along historic U.S. Route 66.
  • D. Collins, Missouri
    Collins, Missouri is a small rural village in St. Clair County known for its location along a major north–south highway in western Missouri.
  • E. Madison, Missouri
    Madison, Missouri is a small city located in Monroe County in the central 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 (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_69d8e8d04d5c8190baa816986f2b1d1e completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e604c84fe08190869463bdd0324160 completed April 20, 2026, 10:49 a.m.
Created at: April 10, 2026, 1:31 p.m.