Triple
T15951971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM-430 |
E386838
|
entity |
| Predicate | informationDisplayedInCab |
P17720
|
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: [TVM-430, informationDisplayedInCab, permitted speed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: informationDisplayedInCab Context triple: [TVM-430, informationDisplayedInCab, permitted speed]
-
A.
hasPassengerInformationSystem
Indicates that an entity is equipped with a system that provides information to passengers, such as schedules, announcements, or travel updates.
-
B.
usedForPassengerInformation
Indicates that something serves the purpose of providing information to passengers.
-
C.
providesInformationIn
chosen
Indicates that one entity supplies or conveys information within or through another entity or context.
-
D.
hasRollingStockOnDisplay
Indicates that a location or entity has railway rolling stock (such as locomotives or carriages) exhibited for public viewing.
-
E.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.