Triple
T1222936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avoca, Iowa |
E26263
|
entity |
| Predicate | hasRoadJunction |
P1018
|
FINISHED |
| Object | junction of Interstate 80 and U.S. Route 59 |
—
|
LITERAL 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: junction of Interstate 80 and U.S. Route 59 | Statement: [Avoca, Iowa, hasRoadJunction, junction of Interstate 80 and U.S. Route 59]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadJunction Context triple: [Avoca, Iowa, hasRoadJunction, junction of Interstate 80 and U.S. Route 59]
-
A.
roadJunctionIncludes
Indicates that a road junction spatially contains or encompasses a specific road segment or related roadway element as part of its structure.
-
B.
hasJunctionWith
chosen
Indicates that one entity meets or intersects with another at a shared junction point.
-
C.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
-
D.
linkedByRoadTo
Indicates that two locations are directly connected to each other by a road suitable for travel.
-
E.
roadTerminusOf
Indicates that a road ends at, or has its terminal point at, the referenced location or route.
- F. None of above.
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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be21a2bc819094b47580d7c5cdf8 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.