Triple
T21779426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DR |
E537671
|
entity |
| Predicate | operatedRailwayStations |
P42386
|
FINISHED |
| Object | railway stations 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 stations in Germany | Statement: [DR, operatedRailwayStations, railway stations in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRailwayStations Context triple: [DR, operatedRailwayStations, railway stations in Germany]
-
A.
operatedStationsIn
Indicates that an entity managed or ran the operations of one or more stations within a specified area or system.
-
B.
operatedStation
chosen
Indicates that one entity managed, ran, or was responsible for the operation of a particular station.
-
C.
isRailwayStationInNetwork
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
D.
railInfrastructureServed
Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
-
E.
railStationManager
Indicates that one entity manages, operates, or is responsible for the administration of a particular railway station.
- 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.