Triple
T32976307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nureddin al-Atassi |
E843670
|
entity |
| Predicate | coupLeaderWhoDeposed |
P50317
|
FINISHED |
| Object | Hafez al-Assad |
—
|
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: Hafez al-Assad | Statement: [Nureddin al-Atassi, coupLeaderWhoDeposed, Hafez al-Assad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coupLeaderWhoDeposed Context triple: [Nureddin al-Atassi, coupLeaderWhoDeposed, Hafez al-Assad]
-
A.
coupLeader
chosen
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
B.
headOfStateDeposed
Indicates that a person who was serving as head of state has been forcibly removed from that position, typically through non-constitutional or coercive means.
-
C.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
-
D.
coupLeaderOpposedBy
Indicates that the identified coup leader is actively resisted, challenged, or opposed by another specified party.
-
E.
coupParticipantIn
Indicates that an entity took part in, contributed to, or was involved in carrying out a specific coup event.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d1aeda688190b0388262b99be7c4 |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:22 a.m.