Triple

T12659363
Position Surface form Disambiguated ID Type / Status
Subject Adams County, Iowa E302375 entity
Predicate countySeat P383 FINISHED
Object Corning, Iowa E776343 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: Corning, Iowa | Statement: [Adams County, Iowa, countySeat, Corning, Iowa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Corning, Iowa
Context triple: [Adams County, Iowa, countySeat, Corning, Iowa]
  • A. Corning, Iowa chosen
    Corning, Iowa is a small city in southwestern Iowa known as the administrative and commercial center of Adams County.
  • B. Conroy, Iowa
    Conroy, Iowa is a small unincorporated community located in Iowa County in the U.S. state of Iowa.
  • C. Williamson, Iowa
    Williamson, Iowa is a small unincorporated rural community located in Lucas County in the south-central part of the state.
  • D. Mineola, Iowa
    Mineola, Iowa is a small unincorporated rural community located in southwestern Iowa.
  • E. 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.
  • 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_69d7bded71a88190bb76e2413af9ea66 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d961636db8819099c438b24bcfd866 completed April 10, 2026, 8:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69f66885e44c8190a650301b0e86d0f4 completed May 2, 2026, 9:11 p.m.
Created at: April 9, 2026, 5:19 p.m.