Triple
T26732218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corrective Movement |
E674003
|
entity |
| Predicate | newLeader |
P161178
|
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: [Corrective Movement, newLeader, Hafez al-Assad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: newLeader Context triple: [Corrective Movement, newLeader, Hafez al-Assad]
-
A.
initialLeader
Indicates that an entity serves as the first or original leader of another entity, typically at the start of its existence or a defined period.
-
B.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
-
C.
promotedLeader
Indicates that one entity has elevated another entity to a higher leadership position or role.
-
D.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
E.
secondLeader
Indicates that an entity serves as the second-ranking leader or deputy leader in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618429e9481908140bb49a3edd6de |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:45 a.m.