Triple
T17169735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siemens Trainguard MT |
E416696
|
entity |
| Predicate | supportsGradeOfAutomation |
P9537
|
FINISHED |
| Object | GoA2 |
—
|
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: GoA2 | Statement: [Siemens Trainguard MT, supportsGradeOfAutomation, GoA2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGradeOfAutomation Context triple: [Siemens Trainguard MT, supportsGradeOfAutomation, GoA2]
-
A.
canAutomate
Indicates that one entity has the capability to perform, control, or execute another entity’s process or task automatically without continuous human intervention.
-
B.
automatedIn
Indicates that an action, process, or operation is performed automatically within or by a specified system, context, or environment.
-
C.
automationLevel
chosen
Indicates the degree to which a process, task, or system is performed automatically rather than manually.
-
D.
automatedBy
Indicates that an action, process, or function is carried out or controlled by an automated system or mechanism.
-
E.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91831d88190b262227fc41c9067 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.