Triple
T17224075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy Feenstra |
E418064
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Hull, Iowa |
E15345
|
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: Hull, Iowa | Statement: [Randy Feenstra, residence, Hull, Iowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hull, Iowa Context triple: [Randy Feenstra, residence, Hull, Iowa]
-
A.
Hull, Iowa
chosen
Hull, Iowa is a small city in northwestern Iowa known for its agricultural community and Dutch-American heritage.
-
B.
Hudson, Iowa
Hudson, Iowa is a small city in northeastern Iowa that functions as a suburban community within the Waterloo–Cedar Falls metropolitan area.
-
C.
Hancock, Iowa
Hancock, Iowa is a small rural city located in western Iowa within Pottawattamie County.
-
D.
Hamburg, Iowa
Hamburg, Iowa is a small city in southwestern Iowa known for its agricultural surroundings and location near the Missouri River and the borders of Nebraska and Missouri.
-
E.
Havelock, Iowa
Havelock, Iowa is a small rural city in Pocahontas County in northwestern Iowa.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddfe3bc8190b22cee4fc0590b74 |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170ed74688190b15ef6d7e0cebe86 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:38 a.m.