Triple
T23504406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISIS forces in Iraq |
E572241
|
entity |
| Predicate | usedTerrorism |
P152631
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ISIS forces in Iraq, usedTerrorism, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTerrorism Context triple: [ISIS forces in Iraq, usedTerrorism, true]
-
A.
typeOfTerrorism
Indicates a classification relationship where an act or event is identified as belonging to a specific category or type of terrorism.
-
B.
positionOnTerrorism
Indicates a stance or viewpoint that an entity holds regarding terrorism, such as its causes, legitimacy, or appropriate responses.
-
C.
terroristOrganization
Indicates that an entity is recognized as a group that plans, supports, or carries out acts of terrorism.
-
D.
hasTerroristAntagonist
Indicates that the subject work features an antagonist who is a terrorist or engages in terrorism.
-
E.
hasTerroristOrganization
Indicates that an entity is associated with, belongs to, or functions as a terrorist organization.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a8fedbec8190b183661edaba4cd4 |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:07 p.m.