Triple
T13582846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skitube Alpine Railway |
E324464
|
entity |
| Predicate | reducesRoadTraffic |
P32500
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Skitube Alpine Railway, reducesRoadTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reducesRoadTraffic Context triple: [Skitube Alpine Railway, reducesRoadTraffic, yes]
-
A.
relievesTrafficFrom
chosen
Indicates that one entity reduces or alleviates traffic congestion that would otherwise occur on another entity.
-
B.
significantlyShortensRouteBetween
Indicates that one entity provides a connection between two others that makes the path or travel distance between them substantially shorter than alternative routes.
-
C.
facilitatesTrafficFlowBetween
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
-
D.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
E.
reducedTravelTimeFrom
Indicates that one entity has caused or experienced a decrease in the amount of time required to travel from a specified origin entity.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb031e8048190a5f2ea934308036c |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.