Triple
T17207944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usakos |
E417649
|
entity |
| Predicate | distanceToSwakopmund |
P126410
|
FINISHED |
| Object | approximately 140 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 140 km | Statement: [Usakos, distanceToSwakopmund, approximately 140 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSwakopmund Context triple: [Usakos, distanceToSwakopmund, approximately 140 km]
-
A.
distanceToWindhoek
Indicates the measured or calculated distance between a given entity’s location and the city of Windhoek.
-
B.
distanceFromLüderitz
Indicates the measured spatial distance between an entity and the location of Lüderitz.
-
C.
distanceToEtoshaNationalPark
Indicates the measured spatial distance between a given entity and Etosha National Park.
-
D.
distanceToEtoshaVonLindequistGate_km
Indicates the distance, measured in kilometers, from a given location to the Etosha Von Lindequist Gate.
-
E.
distanceFromSossusvlei
Indicates the measured spatial distance between a given location and Sossusvlei.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dc283648190b2c1f957940024aa |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:38 a.m.