Triple
T16260024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outjo |
E394728
|
entity |
| Predicate | distanceToWindhoek |
P122395
|
FINISHED |
| Object | approximately 300 km northwest of Windhoek |
—
|
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 300 km northwest of Windhoek | Statement: [Outjo, distanceToWindhoek, approximately 300 km northwest of Windhoek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToWindhoek Context triple: [Outjo, distanceToWindhoek, approximately 300 km northwest of Windhoek]
-
A.
distanceFromLüderitz
Indicates the measured spatial distance between an entity and the location of Lüderitz.
-
B.
distanceToGaborone
Indicates the spatial distance between a given entity’s location and the city of Gaborone.
-
C.
distanceToSouthAfrica
Indicates the measured or calculated spatial distance between a given entity and the country of South Africa.
-
D.
distanceToManzini_km
Indicates the physical distance, measured in kilometers, between a given location and Manzini.
-
E.
distanceToBloemfontein
Indicates the spatial distance between a given entity’s location and the city of Bloemfontein.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c3e5388190942b0237ab5d1f0f |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.