Triple
T25649137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mabula Game Reserve |
E643051
|
entity |
| Predicate | approxDriveTimeFromJohannesburg |
P169896
|
FINISHED |
| Object | about 2 to 3 hours |
—
|
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: about 2 to 3 hours | Statement: [Mabula Game Reserve, approxDriveTimeFromJohannesburg, about 2 to 3 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxDriveTimeFromJohannesburg Context triple: [Mabula Game Reserve, approxDriveTimeFromJohannesburg, about 2 to 3 hours]
-
A.
approximateDistanceToJohannesburg
Indicates that one entity has an estimated or rough distance relationship to the location Johannesburg.
-
B.
distanceToJohannesburg_km
Indicates the physical distance, measured in kilometers, between a given entity’s location and Johannesburg.
-
C.
distanceFromCapeTown
Indicates the measured distance between a given location and Cape Town.
-
D.
approximateDistanceToPretoria
Indicates that one entity has an estimated or rough distance measurement relative to the location of Pretoria.
-
E.
distanceFromPretoria
Indicates the spatial distance between a given entity or location and the city of Pretoria.
- 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_69e77e7d8a848190a98d0162325fd780 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 21, 2026, 6:17 p.m.