Triple
T3520844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dartford Tunnel |
E74416
|
entity |
| Predicate | emergencyExits |
P31156
|
FINISHED |
| Object | cross-passages between tunnels |
—
|
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: cross-passages between tunnels | Statement: [Dartford Tunnel, emergencyExits, cross-passages between tunnels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyExits Context triple: [Dartford Tunnel, emergencyExits, cross-passages between tunnels]
-
A.
hasEmergencyExits
chosen
Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
-
B.
numberOfEmergencyExits
Indicates the quantity of emergency exits associated with an entity or location.
-
C.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
D.
evacuationMethod
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
-
E.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc4c6ac8819096e9c773f3cccbfb |
completed | March 8, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69adae10689c8190b7dc6d7daa8295b6 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.