Triple
T36765961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uithuizen railway station |
E908337
|
entity |
| Predicate | distanceFromGroningenCityByRail |
P63224
|
FINISHED |
| Object | approximately 25–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 25–30 km | Statement: [Uithuizen railway station, distanceFromGroningenCityByRail, approximately 25–30 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromGroningenCityByRail Context triple: [Uithuizen railway station, distanceFromGroningenCityByRail, approximately 25–30 km]
-
A.
distanceToGroningenCity_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and the city of Groningen.
-
B.
distanceFromUtrechtCentraal
Indicates the spatial distance between a given location and Utrecht Centraal station.
-
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.
distanceToLeidenCentraal
Indicates the spatial distance between a given location and Leiden Centraal station.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.