Triple
T21779429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DR |
E537671
|
entity |
| Predicate | operatedSignallingSystems |
P40340
|
FINISHED |
| Object | railway signalling in Germany |
—
|
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: railway signalling in Germany | Statement: [DR, operatedSignallingSystems, railway signalling in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedSignallingSystems Context triple: [DR, operatedSignallingSystems, railway signalling in Germany]
-
A.
signallingSystem
Indicates that one entity functions as a signalling system used to transmit information or cues to another entity.
-
B.
usesRailwaySignallingSystem
chosen
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
C.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
D.
railwayLineNumberingSystem
Indicates a system that assigns and manages identifying numbers for railway lines within a rail network.
-
E.
telecommunicationSystem
Indicates a relationship where communication between entities is carried out over a distance using electronic or digital transmission systems.
- 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0462bde288190beef8c4388949132 |
completed | April 28, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.