Triple
T20023139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-Zug |
E494910
|
entity |
| Predicate | trainNumberPrefix |
P30411
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [D-Zug, trainNumberPrefix, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainNumberPrefix Context triple: [D-Zug, trainNumberPrefix, D]
-
A.
railwayLineNumber
Indicates the identifying number assigned to a specific railway line within a rail network.
-
B.
usesTrainNumber
chosen
Indicates that one entity operates, identifies, or references another entity by a specific train number.
-
C.
hasRailwayLineNumber
Indicates the specific identification number assigned to a railway line associated with an entity.
-
D.
trainNumberDirection
Indicates the specific direction in which a train, identified by its train number, is traveling or scheduled to travel.
-
E.
railwayLineNumberingSystem
Indicates a system that assigns and manages identifying numbers for railway lines within a rail network.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628a1ecc8190bf6ee0bedb61e0b8 |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:35 p.m.