Triple
T16315373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simplon Tunnel |
E396158
|
entity |
| Predicate | ventilationSystem |
P41511
|
FINISHED |
| Object | central ventilation gallery |
—
|
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: central ventilation gallery | Statement: [Simplon Tunnel, ventilationSystem, central ventilation gallery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ventilationSystem Context triple: [Simplon Tunnel, ventilationSystem, central ventilation gallery]
-
A.
ventilationFeature
chosen
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
B.
hasVentilationShafts
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
C.
hasVacuumSystem
Indicates that one entity is equipped with, or includes as a component, a vacuum system.
-
D.
containmentVenting
Indicates a relationship where a containment system releases or vents its contents, typically to relieve pressure or prevent overaccumulation.
-
E.
hasVentilationBuildings
Indicates that certain buildings are designated to provide ventilation for another structure, area, or system.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e288de57cc81908cec93309347c385 |
completed | April 17, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.