Triple
T20151744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troyeville, Johannesburg |
E491449
|
entity |
| Predicate | directionFromJohannesburgCBD |
P138870
|
FINISHED |
| Object | east |
—
|
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: east | Statement: [Troyeville, Johannesburg, directionFromJohannesburgCBD, east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromJohannesburgCBD Context triple: [Troyeville, Johannesburg, directionFromJohannesburgCBD, east]
-
A.
directionFromDurbanCBD
Indicates the compass direction in which one location lies relative to the Durban Central Business District (CBD).
-
B.
directionFromCapeTown
Indicates the compass direction in which one entity is located relative to Cape Town.
-
C.
directionWithinGauteng
Indicates a directional relationship where one place or object is located in a specific direction relative to another, with both situated within the Gauteng region.
-
D.
directionFromPerthCBD
Indicates the compass direction in which one entity is located relative to the Perth Central Business District.
-
E.
directionFromCanberraCBD
Indicates the compass direction in which one location lies relative to the Canberra Central Business District (CBD).
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667dc34e081908e42e4c1bde26170 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.