Triple
T29274696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iran–Saudi Arabia rivalry |
E742215
|
entity |
| Predicate | diplomaticBreak |
P158215
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Iran–Saudi Arabia rivalry, diplomaticBreak, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diplomaticBreak Context triple: [Iran–Saudi Arabia rivalry, diplomaticBreak, 2016]
-
A.
diplomaticRelationsInterruptedDuring
chosen
Indicates that formal diplomatic relations between entities were suspended or broken off during a specified time period or event.
-
B.
diplomaticOutcome
Indicates the result or consequence of a diplomatic interaction, negotiation, or relationship between parties.
-
C.
diplomaticPost
Indicates that an entity holds or is assigned to an official diplomatic position or mission representing one state or organization to another.
-
D.
diplomaticType
Indicates the specific category or nature of a diplomatic relationship or role that exists between entities.
-
E.
brokeTreatyWith
Indicates that one party violated the terms of a formal agreement or treaty it had with another party.
- 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_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 12:50 p.m.