Triple
T27369039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barendrecht railway station |
E690255
|
entity |
| Predicate | distanceFromRotterdamCentraal |
P199656
|
FINISHED |
| Object | approximately 7 km south |
—
|
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 7 km south | Statement: [Barendrecht railway station, distanceFromRotterdamCentraal, approximately 7 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromRotterdamCentraal Context triple: [Barendrecht railway station, distanceFromRotterdamCentraal, approximately 7 km south]
-
A.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
B.
distanceFromRotterdamCityCenter
Indicates the measured distance between a given location and the center of Rotterdam.
-
C.
distanceToDenHaagCentraal
Indicates the measured distance between a given location and Den Haag Centraal station.
-
D.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
-
E.
distanceToLeidenCentraal
Indicates the spatial distance between a given location and Leiden 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
| PDg | Predicate description generation | batch_69ff4de56fd48190aefdbf13c70f76ce |
completed | May 9, 2026, 3:08 p.m. |
Created at: April 27, 2026, 12:18 p.m.