Triple
T30813308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mooi River |
E784701
|
entity |
| Predicate | roadDistanceToJohannesburg |
P110771
|
FINISHED |
| Object | approximately 430 kilometres |
—
|
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 430 kilometres | Statement: [Mooi River, roadDistanceToJohannesburg, approximately 430 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadDistanceToJohannesburg Context triple: [Mooi River, roadDistanceToJohannesburg, approximately 430 kilometres]
-
A.
distanceToJohannesburg_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Johannesburg.
-
B.
approxDriveTimeFromJohannesburg
Indicates the estimated amount of time it typically takes to drive from Johannesburg to another location.
-
C.
approximateDistanceToJohannesburg
chosen
Indicates that one entity has an estimated or rough distance relationship to the location Johannesburg.
-
D.
roadDistanceToPietermaritzburg
Indicates the road travel distance between a given place and Pietermaritzburg.
-
E.
approximateDistanceToPretoria
Indicates that one entity has an estimated or rough distance measurement relative to the location of Pretoria.
- 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_69f224b4eda48190bd212ce4f3901e56 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:43 p.m.