Triple
T25072270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuidlaren |
E627946
|
entity |
| Predicate | distanceToAssen |
P173188
|
FINISHED |
| Object | about 14 km north |
—
|
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: about 14 km north | Statement: [Zuidlaren, distanceToAssen, about 14 km north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAssen Context triple: [Zuidlaren, distanceToAssen, about 14 km north]
-
A.
distanceToAmsterdam
Indicates the spatial distance between a given location and the city of Amsterdam.
-
B.
distanceToEindhovenKmApproximate
Indicates the approximate distance, measured in kilometers, between a given entity and Eindhoven.
-
C.
distanceToUtrecht
Indicates the spatial distance between a given entity and the location of Utrecht.
-
D.
distanceToRotterdam
Indicates the measured distance between a given entity’s location and the city of Rotterdam.
-
E.
distanceToLeidenCentraal
Indicates the spatial distance between a given location and Leiden Centraal station.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 18, 2026, 6:17 a.m.