Triple

T6391028
Position Surface form Disambiguated ID Type / Status
Subject Yale, Kansas E143825 entity
Predicate hasName P744 FINISHED
Object Yale, Kansas E143825 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: Yale, Kansas | Statement: [Yale, Kansas, hasName, Yale, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yale, Kansas
Context triple: [Yale, Kansas, hasName, Yale, Kansas]
  • A. Yale, Kansas chosen
    Yale, Kansas is a small unincorporated community located in Crawford County in southeastern Kansas.
  • B. Ellsworth, Kansas
    Ellsworth, Kansas is a small central Kansas city historically known as a 19th-century cattle town and later as the site of institutions such as St. Joseph Military Academy.
  • C. Ellis, Kansas
    Ellis, Kansas is a small city in western Kansas known as the boyhood home of automotive pioneer Walter P. Chrysler and for its railroad heritage.
  • D. Parsons, Kansas
    Parsons, Kansas is a small city in Labette County known historically as a regional railroad hub and industrial center in southeastern Kansas.
  • E. Chanute, Kansas
    Chanute, Kansas is a small city in Neosho County known historically as a regional railroad and industrial hub in southeastern Kansas.
  • 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_69c008db906c819096f3597d55d95432 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0687c7fdc819099cbbb937dec215e completed March 22, 2026, 10:09 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6388b02888190989623c658469a5a completed March 27, 2026, 7:58 a.m.
Created at: March 22, 2026, 4:34 p.m.