Triple
T21882972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zandvoort aan Zee beach |
E540334
|
entity |
| Predicate | distanceFromAmsterdam |
P85383
|
FINISHED |
| Object | approximately 25 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 km | Statement: [Zandvoort aan Zee beach, distanceFromAmsterdam, approximately 25 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAmsterdam Context triple: [Zandvoort aan Zee beach, distanceFromAmsterdam, approximately 25 km]
-
A.
distanceToAmsterdam
chosen
Indicates the spatial distance between a given location and the city of Amsterdam.
-
B.
distanceFromRotterdamCityCenter
Indicates the measured distance between a given location and the center of Rotterdam.
-
C.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
-
D.
distanceToAmsterdamCentraal
Indicates the physical distance between a given location and Amsterdam Centraal station.
-
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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e890088190aa3023c78a99a536 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7:05 p.m.