Triple
T21657382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Highway 2 |
E534501
|
entity |
| Predicate | easternTerminusJunctionWith |
P50561
|
FINISHED |
| Object | U.S. Route 61 |
—
|
NE NERFINISHED |
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: U.S. Route 61 | Statement: [Iowa Highway 2, easternTerminusJunctionWith, U.S. Route 61]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternTerminusJunctionWith Context triple: [Iowa Highway 2, easternTerminusJunctionWith, U.S. Route 61]
-
A.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
B.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
C.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
D.
terminusJunction
chosen
Indicates a relationship where a route, line, or path ends at a junction point that serves as its terminal connection.
-
E.
terminusProvinceEast
Indicates that something’s eastern endpoint or terminus lies within a particular province.
- 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_69e0c467e1f48190af2650b19175abc4 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5919c9c88190a2ddcf2cefee79a5 |
completed | April 27, 2026, 12:39 p.m. |
| PD | Predicate disambiguation | batch_69e696826c3c81909270791e79760937 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:36 p.m.