Triple
T8158490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salsberry Pass |
E190512
|
entity |
| Predicate | hasRoadFeature |
P1777
|
FINISHED |
| Object | winding roadway |
—
|
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: winding roadway | Statement: [Salsberry Pass, hasRoadFeature, winding roadway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadFeature Context triple: [Salsberry Pass, hasRoadFeature, winding roadway]
-
A.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
-
B.
hasRoadStandard
Indicates that a road or roadway segment conforms to, or is governed by, a specific road design, construction, or operational standard.
-
C.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
D.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
E.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455213f08190a4327a2116c7381f |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.