Triple
T31961737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geldermalsen railway station |
E816057
|
entity |
| Predicate | distanceFromDenBosch |
P203986
|
FINISHED |
| Object | approximately 30 km |
—
|
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 30 km | Statement: [Geldermalsen railway station, distanceFromDenBosch, approximately 30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDenBosch Context triple: [Geldermalsen railway station, distanceFromDenBosch, approximately 30 km]
-
A.
distanceFromTilburgCentral
Indicates the spatial distance between an entity and Tilburg Central (e.g., the central station or central point of Tilburg).
-
B.
distanceFromRotterdamCityCenter
Indicates the measured distance between a given location and the center of Rotterdam.
-
C.
distanceFromRotterdamCentraal
Indicates the measured spatial distance between a given location and Rotterdam Centraal station.
-
D.
distanceToDenHaagCentraal
Indicates the measured distance between a given location and Den Haag Centraal station.
-
E.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a030425fa1c81908748583513552d2b |
completed | May 12, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0303ced28081908588b8a14c23efe9 |
completed | May 12, 2026, 10:41 a.m. |
| PDg | Predicate description generation | batch_6a030424ef5c8190996818517b3e3d51 |
completed | May 12, 2026, 10:42 a.m. |
Created at: May 1, 2026, 12:09 a.m.