Triple
T25339302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quetta Shura |
E635365
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurgent organization leadership |
C41664
|
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: insurgent organization leadership Context triple: [Quetta Shura, instanceOf, insurgent organization leadership]
-
A.
resistance movement leadership
chosen
Resistance movement leadership is the coordinated guidance, decision-making, and inspiration provided by individuals or groups who organize, direct, and sustain collective efforts against an occupying power, oppressive regime, or systemic injustice.
-
B.
guerrilla leader
A guerrilla leader is a commander who organizes, directs, and motivates small, irregular combat groups to conduct unconventional warfare, often using hit-and-run tactics and local support against a typically stronger adversary.
-
C.
paramilitary leader
A paramilitary leader is an individual who commands, organizes, and directs a non-regular, often politically motivated armed group that operates with military-style structure, tactics, and discipline outside or alongside official state forces.
-
D.
rebellious leader
A rebellious leader is a defiant figure who challenges established authority and inspires others to resist and pursue radical change.
-
E.
revolutionary organization role
A revolutionary organization role is a defined position within a movement or group dedicated to radically transforming existing social, political, or economic structures through coordinated, often disruptive, collective action.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:32 p.m.