Triple

T1882376
Position Surface form Disambiguated ID Type / Status
Subject Raymore, Missouri E39880 entity
Predicate locatedNear P294 FINISHED
Object Belton, Missouri E4804 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: Belton, Missouri | Statement: [Raymore, Missouri, locatedNear, Belton, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Belton, Missouri
Context triple: [Raymore, Missouri, locatedNear, Belton, Missouri]
  • A. Belton, Missouri, United States chosen
    Belton, Missouri, United States is a small city in the Kansas City metropolitan area known in part as the burial place of self-improvement pioneer Dale Carnegie.
  • B. Sibley, Missouri
    Sibley, Missouri is a small village in western Missouri known for its proximity to the historic Fort Osage site along the Missouri River.
  • C. Buckner, Missouri
    Buckner, Missouri is a small city located in eastern Jackson County within the Kansas City metropolitan area.
  • D. Gladstone, Missouri
    Gladstone, Missouri is a suburban city in the Kansas City metropolitan area known for its residential neighborhoods and community-oriented services.
  • E. Levasy, Missouri
    Levasy, Missouri is a small rural city located in eastern Jackson County within the Kansas City metropolitan area.
  • 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_69a88633e4fc8190b7eb40463e048ec5 completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69abb0fd4d6881908b8266bdae1517ce completed March 7, 2026, 5 a.m.
NED1 Entity disambiguation (via context triple) batch_69adfba6e94c8190ad1daafbe7f70a44 completed March 8, 2026, 10:43 p.m.
Created at: March 4, 2026, 7:34 p.m.