Triple

T15459291
Position Surface form Disambiguated ID Type / Status
Subject Ford Kansas City Assembly Plant E371854 entity
Predicate location P40 FINISHED
Object Claycomo, Missouri E75875 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: Claycomo, Missouri | Statement: [Ford Kansas City Assembly Plant, location, Claycomo, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Claycomo, Missouri
Context triple: [Ford Kansas City Assembly Plant, location, Claycomo, Missouri]
  • A. Claycomo, Missouri chosen
    Claycomo, Missouri is a small suburban village in the Kansas City metropolitan area known primarily for its Ford Motor Company assembly plant.
  • B. Kenoma, Missouri
    Kenoma, Missouri is a small rural unincorporated community located in Barton County in the southwestern part of the state.
  • C. Auxvasse, Missouri
    Auxvasse, Missouri is a small city in central Missouri known for its rural character and location within Callaway County.
  • D. Elkhorn, Missouri
    Elkhorn, Missouri is a small unincorporated rural community located in Ray County in the U.S. state of Missouri.
  • E. Calhoun, Missouri
    Calhoun, Missouri is a small rural village located in Henry County in the west-central region of the state.
  • 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_69d85cc8bd308190886949510b42e764 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f1623f0819086f6fc2bfd536609 completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff21b9817c819082e5c571b08bafb5 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:32 a.m.