Triple
T21886585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZUB |
E540420
|
entity |
| Predicate | railwaySignallingFunction |
P50536
|
FINISHED |
| Object | train protection |
—
|
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: train protection | Statement: [ZUB, railwaySignallingFunction, train protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwaySignallingFunction Context triple: [ZUB, railwaySignallingFunction, train protection]
-
A.
usesRailwaySignallingSystem
Indicates that one entity operates or applies a particular railway signalling system in the context of train or rail traffic control.
-
B.
railwaySign
chosen
Indicates that one entity functions as a railway-related sign or signal that conveys information or instructions within a rail transport context to another entity.
-
C.
railwaySignificance
Indicates the importance or role that a railway or rail-related feature has within a transportation network, region, or context.
-
D.
railwayStationFunction
Indicates that an entity serves as a railway station and specifies the role or function it performs within the railway network.
-
E.
railwaySignColor
Indicates the color attribute assigned to a particular railway sign.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118ed35948190bbffba2c40029eee |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.