Triple
T28948800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Gulf crisis |
E730950
|
entity |
| Predicate | mainAggressor |
P695
|
FINISHED |
| Object | Iraq |
—
|
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: Iraq | Statement: [Persian Gulf crisis, mainAggressor, Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAggressor Context triple: [Persian Gulf crisis, mainAggressor, Iraq]
-
A.
mainAttacker
chosen
Indicates that an entity is the primary or leading aggressor responsible for initiating or carrying out an attack against another entity.
-
B.
mainPersecutor
Indicates that one entity is the primary agent responsible for persecuting or oppressing another entity.
-
C.
antagonistInvolved
Indicates that an antagonist participates in, influences, or is otherwise actively involved in the referenced event or situation.
-
D.
assaultLedBy
Indicates that an assault was directed or coordinated by a particular person or group.
-
E.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 8:42 a.m.