Triple
T34719040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dujail massacre |
E1000859
|
entity |
| Predicate | chargeUsedInTrialOf |
P181542
|
FINISHED |
| Object | Saddam Hussein |
—
|
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: Saddam Hussein | Statement: [Dujail massacre, chargeUsedInTrialOf, Saddam Hussein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeUsedInTrialOf Context triple: [Dujail massacre, chargeUsedInTrialOf, Saddam Hussein]
-
A.
chargeOftenUsed
Indicates that an entity is frequently subjected to or associated with a particular charge (such as a legal, financial, or electrical charge).
-
B.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
C.
budgetChargedOn
Indicates that a specific budget is debited or applied as the source of funds for a given cost, transaction, or activity.
-
D.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
E.
numberOfCharges
Indicates the count of distinct charges, accusations, or fee items associated with an entity or event.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.