Triple

T4239965
Position Surface form Disambiguated ID Type / Status
Subject Mission, Kansas E95387 entity
Predicate adjacentTo P224 FINISHED
Object Fairway, Kansas E335569 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: Fairway, Kansas | Statement: [Mission, Kansas, adjacentTo, Fairway, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Fairway, Kansas
Context triple: [Mission, Kansas, adjacentTo, Fairway, Kansas]
  • A. Fairway, Kansas chosen
    Fairway, Kansas is a small residential city in the Kansas City metropolitan area known for its quiet neighborhoods and proximity to urban amenities.
  • B. Woodbine, Kansas
    Woodbine, Kansas is a small rural community located in central Kansas within Dickinson County.
  • C. Westwood, Kansas
    Westwood, Kansas is a small suburban city in the Kansas City metropolitan area known for its residential neighborhoods and proximity to downtown Kansas City.
  • D. Mission, Kansas
    Mission, Kansas is a small suburban city in Johnson County that forms part of the Kansas City metropolitan area.
  • E. Franklin, Kansas
    Franklin, Kansas is a small unincorporated community in southeastern Kansas known historically as a coal mining town.
  • 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_69b3453d91548190b4d4ef8fe52aa2ac completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e77fb5c8190b298818acb68ff63 completed March 12, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdacc9ef8c81909ff2a16cf68844d0 completed March 20, 2026, 8:23 p.m.
Created at: March 12, 2026, 11:05 p.m.