Triple
T2278171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truth and Reconciliation Commission reports |
E51219
|
entity |
| Predicate | typeOfTruthCommissionOutput |
P11602
|
FINISHED |
| Object | final report |
—
|
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: final report | Statement: [Truth and Reconciliation Commission reports, typeOfTruthCommissionOutput, final report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTruthCommissionOutput Context triple: [Truth and Reconciliation Commission reports, typeOfTruthCommissionOutput, final report]
-
A.
finalReportType
chosen
Indicates the specific category or format assigned to a report when it is in its final, completed state.
-
B.
courtReported
Indicates that a court’s decision, proceedings, or judgment have been formally documented and made publicly available in a report or record.
-
C.
typeOfTrust
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
D.
typeOfSanction
Indicates the specific category or kind of sanction that is applied in a given situation.
-
E.
reporterType
Indicates the specific role or category of reporter associated with an entity or event.
- 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc217b6648190be77d2176d322efd |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.