Triple
T24058736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceneri Base Tunnel |
E595881
|
entity |
| Predicate | ETCSLevel |
P40340
|
FINISHED |
| Object | Level 2 |
—
|
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: Level 2 | Statement: [Ceneri Base Tunnel, ETCSLevel, Level 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ETCSLevel Context triple: [Ceneri Base Tunnel, ETCSLevel, Level 2]
-
A.
hasRailLevel
Indicates that one entity possesses, is assigned, or is associated with a specific rail-related level or classification in relation to another entity.
-
B.
hasAutomaticTrainControlCompatibility
Indicates that an entity is compatible with, or supports integration with, an automatic train control (ATC) system.
-
C.
railroadHierarchyLevel
Indicates the position or rank of a railroad-related entity within an ordered organizational or structural hierarchy.
-
D.
usesRailwaySignallingSystem
chosen
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
E.
hasAutomaticTrainControl
Indicates that an entity is equipped with or uses an automatic train control system for managing train operations.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da52b9d48190b503fad5ff70e4c6 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:36 p.m.