Triple
T23553634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostkreuz |
E578119
|
entity |
| Predicate | servedByRegionalLine |
P1293
|
FINISHED |
| Object | RE1 |
—
|
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: RE1 | Statement: [Ostkreuz, servedByRegionalLine, RE1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByRegionalLine Context triple: [Ostkreuz, servedByRegionalLine, RE1]
-
A.
servedByRailBranch
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
-
B.
servedByLine
chosen
Indicates that a transportation stop, station, or location is provided service by a specific transit line.
-
C.
servedByTramwayLine
Indicates that a location or area is provided public transport service by a specific tramway line.
-
D.
lineServed
Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
-
E.
servesCommuterRailLine
Indicates that a location or facility provides access to and is a stop or station for a commuter rail line.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed17fc881908b45dcde14790d42 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.