Triple
T31012399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 1 |
E790240
|
entity |
| Predicate | speedSupervisionType |
P170908
|
FINISHED |
| Object | continuous on-board supervision |
—
|
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: continuous on-board supervision | Statement: [ETCS Level 1, speedSupervisionType, continuous on-board supervision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedSupervisionType Context triple: [ETCS Level 1, speedSupervisionType, continuous on-board supervision]
-
A.
speedSupervision
Indicates a relationship where an entity monitors, controls, or enforces limits on the speed of another entity or process.
-
B.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
C.
hasSpeedRegime
Indicates a relationship where an entity is associated with a particular speed range or operating speed condition under which it functions or is evaluated.
-
D.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
E.
speedDependsOn
Indicates that the speed of one entity is determined or influenced by another specified factor or entity.
- F. None of above. chosen
Provenance (4 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:57 p.m.