Triple
T23364205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Capture Inquiry |
E593266
|
entity |
| Predicate | reportDeliveredTo |
P1386
|
FINISHED |
| Object | Cyril Ramaphosa |
—
|
NE NERFINISHED |
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: Cyril Ramaphosa | Statement: [State Capture Inquiry, reportDeliveredTo, Cyril Ramaphosa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportDeliveredTo Context triple: [State Capture Inquiry, reportDeliveredTo, Cyril Ramaphosa]
-
A.
deliveryConfirmation
Indicates that a delivery has been successfully completed and acknowledged, confirming that the intended recipient has received the item or shipment.
-
B.
delivered
chosen
Indicates that something has been brought or transported to a recipient or destination, typically completing a transfer or fulfillment of an order, message, or service.
-
C.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
D.
deliveredAs
Indicates that something is provided, transmitted, or presented in a particular form, manner, or role.
-
E.
reasonNotDelivered
Indicates that there exists an explanation or cause for why a planned or expected delivery did not occur.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aac4248190a4663ed12aed6856 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.