Triple

T11723710
Position Surface form Disambiguated ID Type / Status
Subject Shelby County, Iowa E278703 entity
Predicate hasSettlement P1068 FINISHED
Object Elk Horn, Iowa E157803 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: Elk Horn, Iowa | Statement: [Shelby County, Iowa, hasSettlement, Elk Horn, Iowa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Elk Horn, Iowa
Context triple: [Shelby County, Iowa, hasSettlement, Elk Horn, Iowa]
  • A. Elk Horn, Iowa chosen
    Elk Horn, Iowa is a small rural city in western Iowa known for its strong Danish heritage and cultural attractions.
  • B. Hornick, Iowa
    Hornick, Iowa is a small rural city in western Iowa known for its location near the Missouri River and history of flooding and flood-mitigation efforts.
  • C. Havelock, Iowa
    Havelock, Iowa is a small rural city in Pocahontas County in northwestern Iowa.
  • D. Elkhorn, Nebraska
    Elkhorn, Nebraska is a suburban community in Douglas County that has been annexed by the city of Omaha and is known for its residential neighborhoods and proximity to the Elkhorn River.
  • E. Sibley, Iowa
    Sibley, Iowa is a small city in northwestern Iowa that serves as the administrative and commercial hub of Osceola County.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4d603cc8190b2e68d0bdd793362 completed April 10, 2026, 7:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69ef83d9fe70819089b9f3585188f96c completed April 27, 2026, 3:42 p.m.
Created at: April 8, 2026, 9:41 p.m.