Triple
T30626192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howick |
E779583
|
entity |
| Predicate | distanceFromPietermaritzburg |
P203192
|
FINISHED |
| Object | approximately 20–30 km northwest |
—
|
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–30 km northwest | Statement: [Howick, distanceFromPietermaritzburg, approximately 20–30 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromPietermaritzburg Context triple: [Howick, distanceFromPietermaritzburg, approximately 20–30 km northwest]
-
A.
roadDistanceToPietermaritzburg
Indicates the road travel distance between a given place and Pietermaritzburg.
-
B.
distanceFromMahikeng
Indicates the measured distance between a given entity and the location of Mahikeng.
-
C.
distanceFromPretoria
Indicates the spatial distance between a given entity or location and the city of Pretoria.
-
D.
distanceToDurban_km
Indicates the physical distance, measured in kilometers, between a given location and the city of Durban.
-
E.
distanceToJohannesburg_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Johannesburg.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01378bf05c8190af9f5e06a2810c7d |
completed | May 11, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_6a0137277c6c8190bcec341f2a0757c4 |
completed | May 11, 2026, 1:55 a.m. |
| PDg | Predicate description generation | batch_6a01378b165c8190b7b738da4e1ab36b |
completed | May 11, 2026, 1:57 a.m. |
Created at: April 29, 2026, 8:28 p.m.