Triple
T23553633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ostkreuz |
E578119
|
entity |
| Predicate | hasRegionalTrainService |
P152769
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ostkreuz, hasRegionalTrainService, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalTrainService Context triple: [Ostkreuz, hasRegionalTrainService, yes]
-
A.
hasNightTrainService
Indicates that a transportation route or station is served by trains that operate during nighttime hours.
-
B.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
C.
railwayTypeServed
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
-
D.
servesLocalTrains
Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
-
E.
hasLocalRailOperator
Indicates that a specified rail operator is responsible for providing local or regional rail services within a particular area or network.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.