Triple
T25478558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Bramstedt |
E638501
|
entity |
| Predicate | distanceToKiel |
P88937
|
FINISHED |
| Object | approximately 50 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 50 km south | Statement: [Bad Bramstedt, distanceToKiel, approximately 50 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKiel Context triple: [Bad Bramstedt, distanceToKiel, approximately 50 km south]
-
A.
distanceToKiel_km
chosen
Indicates the physical distance, measured in kilometers, between a given place and the city of Kiel.
-
B.
distanceToKielce
Indicates the spatial distance between a given entity and the city of Kielce.
-
C.
distanceToKleve
Indicates the spatial distance between a given entity and the location Kleve.
-
D.
distanceToFlensburg_km
Indicates the distance, measured in kilometers, between a given entity’s location and the city of Flensburg.
-
E.
distanceToKassel
Indicates the spatial distance between a given entity and the location Kassel.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 21, 2026, 2:27 p.m.