Triple
T25608106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Highway 82 (Colorado) |
E641967
|
entity |
| Predicate | connectsViaCorridor |
P156541
|
FINISHED |
| Object | Roaring Fork Valley |
—
|
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: Roaring Fork Valley | Statement: [State Highway 82 (Colorado), connectsViaCorridor, Roaring Fork Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsViaCorridor Context triple: [State Highway 82 (Colorado), connectsViaCorridor, Roaring Fork Valley]
-
A.
linkedByCorridor
chosen
Indicates that two locations are directly connected to each other by a corridor.
-
B.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
C.
passagewayConnection
Indicates a relationship where one passageway provides a direct route or link between two locations or spaces.
-
D.
isPartOfCorridorSystem
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
E.
inCorridor
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 21, 2026, 4:39 p.m.