Triple
T24656745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevelaer |
E610413
|
entity |
| Predicate | distanceToDuisburg |
P157811
|
FINISHED |
| Object | approximately 50 km northwest |
—
|
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 northwest | Statement: [Kevelaer, distanceToDuisburg, approximately 50 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDuisburg Context triple: [Kevelaer, distanceToDuisburg, approximately 50 km northwest]
-
A.
distanceToDortmund
Indicates the spatial distance between a given entity’s location and the city of Dortmund.
-
B.
distanceToWuppertal
Indicates the spatial distance between a given entity and the location of Wuppertal.
-
C.
distanceToHamburg
Indicates the spatial distance between a given entity’s location and the city of Hamburg.
-
D.
distanceToKoblenz
Indicates the spatial distance between a given entity and the location of Koblenz.
-
E.
distanceToKleve
Indicates the spatial distance between a given entity and the location Kleve.
- 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 2:34 a.m.