Triple
T7915345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorinchem |
E183810
|
entity |
| Predicate | distanceToUtrecht |
P79757
|
FINISHED |
| Object | approximately 30 kilometers 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 30 kilometers south | Statement: [Gorinchem, distanceToUtrecht, approximately 30 kilometers south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToUtrecht Context triple: [Gorinchem, distanceToUtrecht, approximately 30 kilometers south]
-
A.
roadDistanceToUtrecht_km
Indicates the distance in kilometers between an entity and Utrecht when traveling by road.
-
B.
distanceToEindhovenKmApproximate
Indicates the approximate distance, measured in kilometers, between a given entity and Eindhoven.
-
C.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
D.
distanceFromRotterdamCityCenter
Indicates the measured distance between a given location and the center of Rotterdam.
-
E.
distanceToLeiden
Indicates the measured spatial distance between a given entity and the location Leiden.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a759b548190af2e2aa0705d7051 |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:05 p.m.