Triple
T6316737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolbermoor |
E141634
|
entity |
| Predicate | distanceToRosenheim |
P70016
|
FINISHED |
| Object | approximately 5 km west |
—
|
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 5 km west | Statement: [Kolbermoor, distanceToRosenheim, approximately 5 km west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRosenheim Context triple: [Kolbermoor, distanceToRosenheim, approximately 5 km west]
-
A.
distanceToStuttgart
Indicates the measured distance between a given entity’s location and the city of Stuttgart.
-
B.
distanceToNuremberg
Indicates the spatial distance between a given entity and the location of Nuremberg.
-
C.
distanceToBern_km
Indicates the distance, measured in kilometers, between an entity’s location and the city of Bern.
-
D.
distanceToBerlin
Indicates the spatial distance between a given entity’s location and the city of Berlin.
-
E.
distanceToUlm
Indicates the spatial distance between a given entity or location and the city of Ulm.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c25530819080b29e0029175c00 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:29 p.m.