Triple
T26688538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamist uprising in Syria |
E672813
|
entity |
| Predicate | leaderOnGovernmentSide |
P161116
|
FINISHED |
| Object | Rifaat 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: Rifaat al-Assad | Statement: [Islamist uprising in Syria, leaderOnGovernmentSide, Rifaat al-Assad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderOnGovernmentSide Context triple: [Islamist uprising in Syria, leaderOnGovernmentSide, Rifaat al-Assad]
-
A.
leaderOnGovernmentSide
chosen
Indicates that the subject is a leader aligned with, representing, or acting on behalf of the government side in a conflict or political context.
-
B.
hasLeaderInGovernment
Indicates that one entity serves as the leader or head of government for another entity.
-
C.
ledGovernment
Indicates that one entity served as the head or primary leader of the government of another entity.
-
D.
ledToGovernment
Indicates that one entity’s actions, influence, or outcome resulted in another entity attaining or forming a government.
-
E.
positionOnGovernment
Indicates an entity’s stance, role, or status within a governmental structure or political office.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 3:24 a.m.