Triple
T26047599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snekkersten |
E647876
|
entity |
| Predicate | distanceToHelsingør |
P193522
|
FINISHED |
| Object | approximately 4 km 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 4 km south | Statement: [Snekkersten, distanceToHelsingør, approximately 4 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToHelsingør Context triple: [Snekkersten, distanceToHelsingør, approximately 4 km south]
-
A.
distanceToFlensburg_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Flensburg.
-
B.
distanceFromArendal
Indicates the spatial distance between a given entity and the location of Arendal.
-
C.
distanceFromCopenhagen
Indicates the spatial distance between a given entity and the location of Copenhagen.
-
D.
distanceFromLongyearbyen
Indicates the measured distance between a given location and Longyearbyen.
-
E.
distanceToHöxter
Indicates the spatial distance between a given entity or location and the town of Höxter.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: April 22, 2026, 9:10 a.m.