Triple
T2168267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severn Tunnel |
E46960
|
entity |
| Predicate | hasVentilationShaft |
P31158
|
FINISHED |
| Object | Sudbrook shaft |
—
|
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: Sudbrook shaft | Statement: [Severn Tunnel, hasVentilationShaft, Sudbrook shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVentilationShaft Context triple: [Severn Tunnel, hasVentilationShaft, Sudbrook shaft]
-
A.
hasVentilationShafts
chosen
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
B.
hasVentilationBuildings
Indicates that certain buildings are designated to provide ventilation for another structure, area, or system.
-
C.
hasFlankVents
Indicates that an entity possesses vents located on its sides or flanks.
-
D.
airShaftsLead
Indicates that one or more air shafts provide a passage or connection that leads from a source location to a destination location.
-
E.
airIntakeType
Indicates the type or configuration of the system or mechanism used to draw air into an engine or device.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.