Triple
T26732324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ba'athist internal power struggle in Syria (1966–1970) |
E674006
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intra-party conflict |
C19129
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: intra-party conflict Context triple: [Ba'athist internal power struggle in Syria (1966–1970), instanceOf, intra-party conflict]
-
A.
faction within political party
chosen
A faction within a political party is an organized subgroup of members who share distinct ideological views, policy priorities, or strategic goals that differentiate them from the party’s broader membership.
-
B.
court faction
A court faction is a group of influential individuals within a royal or imperial court who align around shared interests, loyalties, or ambitions to shape political decisions and power dynamics.
-
C.
intra-state rivalry
Intra-state rivalry is a sustained, competitive relationship between distinct political, social, or armed actors operating within the same state who contest authority, resources, or legitimacy.
-
D.
civil conflict
Civil conflict is a sustained, organized struggle within a country between the state and one or more internal groups, or among such groups themselves, involving political, social, or economic grievances and often resulting in violence.
-
E.
intra-Jewish conflict
Intra-Jewish conflict refers to the historical and contemporary tensions, disagreements, and power struggles among diverse Jewish groups over religious authority, cultural identity, political ideology, and communal norms.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 27, 2026, 3:45 a.m.