Triple

T18621978
Position Surface form Disambiguated ID Type / Status
Subject Rucker, Missouri E455173 entity
Predicate hasFullName P16 FINISHED
Object Rucker, Missouri NE NERFINISHED

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: Rucker, Missouri | Statement: [Rucker, Missouri, hasFullName, Rucker, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rucker, Missouri
Context triple: [Rucker, Missouri, hasFullName, Rucker, Missouri]
  • A. Rucker, Missouri chosen
    Rucker, Missouri is an unincorporated rural community located in Randolph County in the U.S. state of Missouri.
  • B. Buckner, Missouri
    Buckner, Missouri is a small city located in eastern Jackson County within the Kansas City metropolitan area.
  • C. Richards, Missouri
    Richards, Missouri is a small rural village located in western Missouri within Vernon County.
  • D. Riverside, Missouri
    Riverside, Missouri is a small city in Platte County near Kansas City, known for its riverfront location along the Missouri River and its mix of residential areas, industry, and gaming attractions.
  • E. Rinehart, Missouri
    Rinehart, Missouri is a small unincorporated community located in Vernon County in the western part of the U.S. state of Missouri.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d38cc7948190a55ea64e5638994e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e54f020fa08190bd78d72182496b19 completed April 19, 2026, 9:54 p.m.
Created at: April 10, 2026, 11:46 a.m.