Triple
T30953219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 0 |
E788601
|
entity |
| Predicate | hasOnboardFunction |
P179053
|
FINISHED |
| Object | display of basic information to driver |
—
|
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: display of basic information to driver | Statement: [ETCS Level 0, hasOnboardFunction, display of basic information to driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnboardFunction Context triple: [ETCS Level 0, hasOnboardFunction, display of basic information to driver]
-
A.
hasOnboardFeature
Indicates that an entity includes or is equipped with a particular feature as part of its built-in or onboard capabilities.
-
B.
hasOnboardButton
Indicates that one entity is equipped with or includes a button installed on or within it.
-
C.
hasOnboardSwitch
Indicates that one entity is equipped with a built-in switch located on or within it.
-
D.
hasOnboardEffects
Indicates that something produces effects or consequences specifically on board a vehicle, vessel, or similar platform.
-
E.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 29, 2026, 8:53 p.m.