Triple
T26955829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Dujail |
E678900
|
entity |
| Predicate | relatedExecutionDate |
P49637
|
FINISHED |
| Object | 30 December 2006 |
—
|
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: 30 December 2006 | Statement: [Al-Dujail, relatedExecutionDate, 30 December 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedExecutionDate Context triple: [Al-Dujail, relatedExecutionDate, 30 December 2006]
-
A.
sharesExecutionDateWith
Indicates that two or more entities occur or are scheduled to occur on the same execution date.
-
B.
hasExecutionDate
chosen
Indicates that an entity is associated with a specific date on which an execution or carrying out of an action, order, or sentence is scheduled or took place.
-
C.
associatedWorkDate
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
D.
dateOfRelatedEvent
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
E.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: April 27, 2026, 6:27 a.m.