Triple
T37505135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraq Intelligence Commission |
E932069
|
entity |
| Predicate | yearReportDelivered |
P108241
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Iraq Intelligence Commission, yearReportDelivered, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearReportDelivered Context triple: [Iraq Intelligence Commission, yearReportDelivered, 2005]
-
A.
finalReportSubmissionYear
chosen
Indicates the calendar year in which the final report is formally submitted.
-
B.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
C.
reportPeriod
Indicates the specific time span or interval to which a report’s data or findings apply.
-
D.
TRCReportYear
Indicates the specific year in which a Truth and Reconciliation Commission (TRC) report was issued, published, or is associated with.
-
E.
reportsOutcomeOf
Indicates that one entity communicates or provides the result, consequence, or final status of another entity’s process, event, or action.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.