Triple
T9299468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar diplomatic crisis 2017 |
E223721
|
entity |
| Predicate | accusationByBlockadingStates |
P87925
|
FINISHED |
| Object | support for terrorism |
—
|
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: support for terrorism | Statement: [Qatar diplomatic crisis 2017, accusationByBlockadingStates, support for terrorism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusationByBlockadingStates Context triple: [Qatar diplomatic crisis 2017, accusationByBlockadingStates, support for terrorism]
-
A.
accusesOfTyranny
Indicates that one entity asserts or charges that another entity is acting in a tyrannical or oppressive manner.
-
B.
blockadeImpact
Indicates the effect or consequences that a blockade has on the targeted entities or systems.
-
C.
blockadeType
Indicates the specific kind or category of blockade involved in the relationship or action.
-
D.
countryAttacked
Indicates that one country has carried out an attack against another country.
-
E.
casusBelliFor
Indicates that one entity serves as the justification or cause for another entity to initiate conflict, often war or hostilities.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08d070c881908bed41aada6f85ae |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:36 p.m.