Triple
T7088348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holacracy |
E165131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational governance system |
C16195
|
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: organizational governance system Context triple: [Holacracy, instanceOf, organizational governance system]
-
A.
corporate governance model
chosen
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.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
organizational policy
An organizational policy is a formal, guiding principle or rule established by an organization to direct decisions, behaviors, and procedures in alignment with its goals, values, and legal obligations.
-
D.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
E.
governance position
A governance position is a formal role within an organization or institution responsible for overseeing decision-making, setting policies, and ensuring accountability and compliance with established rules and objectives.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:41 p.m.