Triple
T31012408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 3 |
E790241
|
entity |
| Predicate | hasControlPrinciple |
P1757
|
FINISHED |
| Object | moving block |
—
|
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: moving block | Statement: [ETCS Level 3, hasControlPrinciple, moving block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasControlPrinciple Context triple: [ETCS Level 3, hasControlPrinciple, moving block]
-
A.
hasGoverningPrinciple
Indicates that one entity is guided, regulated, or constrained by a specific principle, rule, or doctrine that governs its behavior or operation.
-
B.
implementsPrinciple
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
-
C.
usesPrinciple
chosen
Indicates that one entity applies, relies on, or is based upon a particular principle in its functioning, reasoning, or design.
-
D.
hasPrincipleSet
Indicates that an entity is associated with or governed by a specific set of principles.
-
E.
recognizesPrinciple
Indicates that an entity acknowledges the validity, authority, or applicability of a particular principle.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01bb9c33cc8190a95ba124d97edf99 |
completed | May 11, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_6a01bb6772148190a243d1141ad0a237 |
completed | May 11, 2026, 11:20 a.m. |
Created at: April 29, 2026, 8:57 p.m.