Triple
T26754964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurdish democratic confederalism |
E674645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governance model |
C30722
|
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: governance model Context triple: [Kurdish democratic confederalism, instanceOf, governance model]
-
A.
corporate governance model
A corporate governance model is a conceptual framework that defines the structures, processes, and relationships through which a corporation is directed, controlled, and held accountable to its stakeholders.
-
B.
governance doctrine
chosen
A governance doctrine is a coherent set of principles, rules, and practices that defines how authority is structured, decisions are made, and accountability is maintained within an organization or political system.
-
C.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
-
D.
governance program
A governance program is a structured framework of policies, processes, and oversight mechanisms designed to guide decision-making, ensure accountability, manage risk, and align organizational activities with strategic objectives and regulatory requirements.
-
E.
governance network
A governance network is a structured system of interconnected actors—such as governments, organizations, and communities—who collaboratively make, implement, and oversee rules and decisions to guide collective behavior and outcomes.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:55 a.m.