Triple
T5392694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dornach |
E120369
|
entity |
| Predicate | distanceToBasel |
P55051
|
FINISHED |
| Object | approximately 10 km south of Basel |
—
|
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 10 km south of Basel | Statement: [Dornach, distanceToBasel, approximately 10 km south of Basel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBasel Context triple: [Dornach, distanceToBasel, approximately 10 km south of Basel]
-
A.
distanceToBasel_km
chosen
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Basel.
-
B.
distanceToZurich_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Zurich.
-
C.
distanceToGeneva
Indicates the spatial distance between a given entity and the location of Geneva.
-
D.
distanceToBern_km
Indicates the distance, measured in kilometers, between an entity’s location and the city of Bern.
-
E.
distanceFromBesançonKilometres
Indicates the distance, measured in kilometers, between an entity and the city of Besançon.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.