Triple
T24656743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevelaer |
E610413
|
entity |
| Predicate | distanceToKleve |
P157162
|
FINISHED |
| Object | approximately 15 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 15 km south | Statement: [Kevelaer, distanceToKleve, approximately 15 km south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToKleve Context triple: [Kevelaer, distanceToKleve, approximately 15 km south]
-
A.
distanceToKoblenz
Indicates the spatial distance between a given entity and the location of Koblenz.
-
B.
distanceToCologne
Indicates the spatial distance between a given entity’s location and the city of Cologne.
-
C.
distanceToKiel_km
Indicates the physical distance, measured in kilometers, between a given place and the city of Kiel.
-
D.
distanceToKassel
Indicates the spatial distance between a given entity and the location Kassel.
-
E.
distanceToWuppertal
Indicates the spatial distance between a given entity and the location of Wuppertal.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 2:34 a.m.