Triple
T17339246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lærdal Tunnel |
E421020
|
entity |
| Predicate | hasEmergencyLay-bys |
P29828
|
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: [Lærdal Tunnel, hasEmergencyLay-bys, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmergencyLay-bys Context triple: [Lærdal Tunnel, hasEmergencyLay-bys, yes]
-
A.
hasRoadsideFacility
Indicates that a location or route segment is associated with a facility or service situated along its roadside.
-
B.
hasEmergencyLane
Indicates that a road, route, or similar thoroughfare includes a designated emergency lane for use by emergency or breakdown situations.
-
C.
hasRestAreas
chosen
Indicates that a route, location, or facility includes one or more designated rest areas available for use.
-
D.
hasEmergencyTurnarounds
Indicates that a route, roadway, or transportation segment includes designated emergency turnaround areas for authorized vehicles.
-
E.
hasEmergencyServices
Indicates that the subject provides or is equipped with emergency response services (such as police, fire, or medical assistance).
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a14ec90819098db2ac0d58a53e1 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.