Triple
T13058025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truth and Reconciliation Commission |
E327627
|
entity |
| Predicate | finalReportSubmissionYear |
P108241
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Truth and Reconciliation Commission, finalReportSubmissionYear, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalReportSubmissionYear Context triple: [Truth and Reconciliation Commission, finalReportSubmissionYear, 1998]
-
A.
finalPerformanceYear
Indicates the year in which an entity’s performance or activity is recorded or recognized for the last time.
-
B.
finalReportPublicationDate
Indicates the date on which the final report is officially published or made publicly available.
-
C.
finalContractAwardYear
Indicates the calendar year in which the contract was ultimately and officially awarded.
-
D.
finalReportType
Indicates the specific category or format assigned to a report when it is in its final, completed state.
-
E.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980e7ee548190b4b18bdb1357c359 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d980e622e8819087a69bfb1660dd64 |
completed | April 10, 2026, 10:59 p.m. |
Created at: April 9, 2026, 8:58 p.m.