Triple
T21007568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köstendorf |
E517451
|
entity |
| Predicate | distanceToSalzburg |
P131820
|
FINISHED |
| Object | approximately 20 km |
—
|
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 20 km | Statement: [Köstendorf, distanceToSalzburg, approximately 20 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSalzburg Context triple: [Köstendorf, distanceToSalzburg, approximately 20 km]
-
A.
distanceFromSalzburg
chosen
Indicates the spatial distance between a given entity and the city of Salzburg.
-
B.
distanceToInnsbruck
Indicates the spatial distance between a given entity’s location and the city of Innsbruck.
-
C.
distanceToEisenstadt_km
Indicates the physical distance, measured in kilometers, between a given place and Eisenstadt.
-
D.
distanceFromVienna
Indicates the spatial distance between a given entity’s location and the city of Vienna.
-
E.
distanceToRosenheim
Indicates the spatial distance between a given entity and the location Rosenheim.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3cc8648190b1a419ef734a69e6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.