Triple

T11727289
Position Surface form Disambiguated ID Type / Status
Subject south-central Kansas E278803 entity
Predicate containsCity P294 FINISHED
Object Mulvane, Kansas E964153 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: Mulvane, Kansas | Statement: [south-central Kansas, containsCity, Mulvane, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mulvane, Kansas
Context triple: [south-central Kansas, containsCity, Mulvane, Kansas]
  • A. Mulvane, Kansas chosen
    Mulvane, Kansas is a small city in south-central Kansas that functions as a suburban community within the Wichita metropolitan area.
  • B. Langdon, Kansas
    Langdon, Kansas is a small rural community located in Reno County in the central part of the U.S. state of Kansas.
  • C. Marquette, Kansas
    Marquette, Kansas is a small rural city in central Kansas known for its historic downtown and proximity to the Smoky Valley scenic area.
  • D. McLain, Kansas
    McLain, Kansas is a small unincorporated rural community located in Harvey County in the central part of the state.
  • E. Marlborough, Kansas
    Marlborough, Kansas is an unincorporated rural community located in Wichita County in western Kansas, United States.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4d70d908190b5f47c2ef501a191 completed April 10, 2026, 7:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69f6eabf5ed88190b6de7b99b5ab590f completed May 3, 2026, 6:27 a.m.
Created at: April 8, 2026, 9:41 p.m.