Triple
T22939217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilburg Reeshof railway station |
E569671
|
entity |
| Predicate | distanceFromTilburgCentral |
P150331
|
FINISHED |
| Object | approximately 5 km west |
—
|
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: approximately 5 km west | Statement: [Tilburg Reeshof railway station, distanceFromTilburgCentral, approximately 5 km west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTilburgCentral Context triple: [Tilburg Reeshof railway station, distanceFromTilburgCentral, approximately 5 km west]
-
A.
distanceToDenHaagCentraal
Indicates the measured distance between a given location and Den Haag Centraal station.
-
B.
distanceToLeidenCentraal
Indicates the spatial distance between a given location and Leiden Centraal station.
-
C.
distanceFromRotterdamCityCenter
Indicates the measured distance between a given location and the center of Rotterdam.
-
D.
distanceToEindhovenKmApproximate
Indicates the approximate distance, measured in kilometers, between a given entity and Eindhoven.
-
E.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181378660819083239986c846ec17 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:45 p.m.