Triple
T29274705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Saudi Arabia rivalry |
E742215
|
entity |
| Predicate | affectsOrganization |
P142521
|
FINISHED |
| Object | Gulf Cooperation Council |
—
|
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: Gulf Cooperation Council | Statement: [Iran–Saudi Arabia rivalry, affectsOrganization, Gulf Cooperation Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsOrganization Context triple: [Iran–Saudi Arabia rivalry, affectsOrganization, Gulf Cooperation Council]
-
A.
affectedCompany
Indicates that a company is impacted or influenced by a particular event, action, or entity.
-
B.
allyOrganization
Indicates that one organization has a cooperative or supportive alliance relationship with another organization.
-
C.
associatedOrganizationFocus
Indicates that an organization is linked to or concerned with a particular area of activity, topic, or domain as a primary focus.
-
D.
affectedAgency
Indicates that one entity has an effect on, or causes a change in, the agency or capacity for action of another entity.
-
E.
alsoAffects
chosen
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
- 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_69f0912124d48190a046642b69407f4c |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 12:50 p.m.