Triple

T14579966
Position Surface form Disambiguated ID Type / Status
Subject Westwood, Kansas E342164 entity
Predicate borderWith P224 FINISHED
Object Mission Woods, Kansas E386877 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: Mission Woods, Kansas | Statement: [Westwood, Kansas, borderWith, Mission Woods, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mission Woods, Kansas
Context triple: [Westwood, Kansas, borderWith, Mission Woods, Kansas]
  • A. Mission Woods, Kansas chosen
    Mission Woods, Kansas is a tiny, affluent residential city in Johnson County that forms part of the Kansas City metropolitan area.
  • B. Mission, Kansas
    Mission, Kansas is a small suburban city in Johnson County that forms part of the Kansas City metropolitan area.
  • C. Mission Hills, Kansas
    Mission Hills, Kansas is an affluent, primarily residential suburb of Kansas City known for its historic estates, country clubs, and tree-lined streets.
  • D. Woodbine, Kansas
    Woodbine, Kansas is a small rural community located in central Kansas within Dickinson County.
  • E. Wakarusa, Kansas
    Wakarusa, Kansas is a small unincorporated rural community located in Shawnee County in the northeastern part 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_69d822ddc0f081909cd8163c7de298cd completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3f6f78c81908a30ecb4c025299d completed April 14, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd94b832b08190965b727baa700403 completed May 8, 2026, 7:46 a.m.
Created at: April 10, 2026, 1:24 a.m.