Triple
T30989337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar–Saudi Arabia relations |
E789622
|
entity |
| Predicate | blockadeImposedBy |
P68236
|
FINISHED |
| Object | Saudi Arabia |
—
|
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: Saudi Arabia | Statement: [Qatar–Saudi Arabia relations, blockadeImposedBy, Saudi Arabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockadeImposedBy Context triple: [Qatar–Saudi Arabia relations, blockadeImposedBy, Saudi Arabia]
-
A.
blockadeType
Indicates the specific kind or category of blockade involved in the relationship or action.
-
B.
blockadeYear
Indicates the year in which a blockade was initiated, imposed, or in effect for the related entities.
-
C.
blockadeImpact
Indicates the effect or consequences that a blockade has on the targeted entities or systems.
-
D.
accusationByBlockadingStates
Indicates that certain states enforcing a blockade are the ones making an accusation against another party.
-
E.
blockadedBy
chosen
Indicates that an entity is prevented from access, movement, or operation by another entity imposing a blockade.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:56 p.m.