Triple
T31012400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ETCS Level 1 |
E790240
|
entity |
| Predicate | movementAuthorityUpdate |
P175380
|
FINISHED |
| Object | discrete locations |
—
|
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: discrete locations | Statement: [ETCS Level 1, movementAuthorityUpdate, discrete locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementAuthorityUpdate Context triple: [ETCS Level 1, movementAuthorityUpdate, discrete locations]
-
A.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
B.
movementDescriptor
Indicates how an entity moves or the manner in which its movement is characterized in relation to another entity or context.
-
C.
movementDomain
Indicates the general area, medium, or context within which a movement or motion takes place.
-
D.
movementStatus
Indicates the current state or condition of an entity’s movement, such as whether and how it is moving or stationary.
-
E.
movementSystem
Indicates a relationship where an entity is part of, uses, or is governed by a particular system that enables or controls its movement.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 8:57 p.m.