Triple
T9270022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 2 |
E222799
|
entity |
| Predicate | informationProvidedToDriver |
P75992
|
FINISHED |
| Object | permitted speed |
—
|
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: permitted speed | Statement: [ETCS Level 2, informationProvidedToDriver, permitted speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationProvidedToDriver Context triple: [ETCS Level 2, informationProvidedToDriver, permitted speed]
-
A.
providedInformationTo
chosen
Indicates that one entity has supplied or communicated information to another entity.
-
B.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
-
C.
usedForPassengerInformation
Indicates that something serves the purpose of providing information to passengers.
-
D.
requiredInformation
Indicates that certain data or details are necessary and must be provided for a process, action, or relationship to proceed or be valid.
-
E.
hasPassengerInformationSystem
Indicates that an entity is equipped with a system that provides information to passengers, such as schedules, announcements, or travel updates.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd078525308190abfb883123742d3f |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.