Triple
T27438881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noordwijkerhout |
E690867
|
entity |
| Predicate | distanceToAmsterdam_km |
P85383
|
FINISHED |
| Object | approximately 35 |
—
|
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 35 | Statement: [Noordwijkerhout, distanceToAmsterdam_km, approximately 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAmsterdam_km Context triple: [Noordwijkerhout, distanceToAmsterdam_km, approximately 35]
-
A.
distanceToAmsterdam
chosen
Indicates the spatial distance between a given location and the city of Amsterdam.
-
B.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
C.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
-
D.
distanceToBudapest_km
Indicates the physical distance, measured in kilometers, between a given location and Budapest.
-
E.
distanceToUtrecht
Indicates the spatial distance between a given entity and the location of Utrecht.
- 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_69ef5200fa0481908e28508d6e2c149e |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff6a4ce9a08190b98abde3a170dd69 |
completed | May 9, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69ff69c11634819089d1084bd2c11534 |
completed | May 9, 2026, 5:07 p.m. |
Created at: April 27, 2026, 12:44 p.m.