Triple

T4239966
Position Surface form Disambiguated ID Type / Status
Subject Mission, Kansas E95387 entity
Predicate adjacentTo P224 FINISHED
Object Merriam, Kansas E95887 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: Merriam, Kansas | Statement: [Mission, Kansas, adjacentTo, Merriam, Kansas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Merriam, Kansas
Context triple: [Mission, Kansas, adjacentTo, Merriam, Kansas]
  • A. Merriam, Kansas chosen
    Merriam, Kansas is a small suburban city in Johnson County that forms part of the greater 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. De Soto, Kansas
    De Soto, Kansas is a small city in northeastern Kansas that forms part of the Kansas City metropolitan area.
  • D. 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.
  • E. McCune, Kansas
    McCune, Kansas is a small rural city located in southeastern Kansas within the Pittsburg micropolitan 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_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_69bdb8f4eab88190b123aca20feb8d63 completed March 20, 2026, 9:15 p.m.
Created at: March 12, 2026, 11:05 p.m.