Triple
T16694760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altoona, Iowa |
E405684
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Bondurant, Iowa |
E400203
|
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: Bondurant, Iowa | Statement: [Altoona, Iowa, hasNearbyCity, Bondurant, Iowa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bondurant, Iowa Context triple: [Altoona, Iowa, hasNearbyCity, Bondurant, Iowa]
-
A.
Bondurant, Iowa
chosen
Bondurant, Iowa is a small but growing suburban city in central Iowa located just northeast of Des Moines.
-
B.
Randalia, Iowa
Randalia, Iowa is a small rural city located in northeastern Iowa within Fayette County.
-
C.
Dunlap, Iowa
Dunlap, Iowa is a small rural city in western Iowa known for its agricultural community and historic downtown.
-
D.
Van Horne, Iowa
Van Horne, Iowa is a small rural city located in eastern Iowa within the Cedar Rapids metropolitan area.
-
E.
Lowden, Iowa
Lowden, Iowa is a small rural city in eastern Iowa known for its agricultural surroundings and tight-knit community.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eacfa788190a8d2058f96c0d445 |
completed | April 18, 2026, 12:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00919acd308190a3f29040554b9cfc |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 10, 2026, 5:19 a.m.