Triple
T8750792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Iowa |
E207951
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Sully, Iowa |
E415554
|
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: Sully, Iowa | Statement: [Central Iowa, hasCity, Sully, Iowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sully, Iowa Context triple: [Central Iowa, hasCity, Sully, Iowa]
-
A.
Sibley, Iowa
Sibley, Iowa is a small city in northwestern Iowa that serves as the administrative and commercial hub of Osceola County.
-
B.
Sutherland, Iowa
Sutherland, Iowa is a small rural city in O'Brien County in northwestern Iowa.
-
C.
City of Sully, Iowa
chosen
The City of Sully is a small rural community in central Iowa known for its agricultural surroundings and tight-knit local character.
-
D.
Hudson, Iowa
Hudson, Iowa is a small city in northeastern Iowa that functions as a suburban community within the Waterloo–Cedar Falls metropolitan area.
-
E.
McClelland, Iowa
McClelland, Iowa is a small rural community located in Pottawattamie County in the western part of the state.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da774f4819099e5bfd12973d946 |
completed | March 31, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfab4d5a2c81909494c119e1d80b4b |
completed | April 3, 2026, 11:58 a.m. |
Created at: March 30, 2026, 6:39 p.m.