Triple
T31646154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECOSOCC Rules of Procedure |
E807589
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational governance document |
C40234
|
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 document Context triple: [ECOSOCC Rules of Procedure, instanceOf, organizational governance document]
-
A.
governance handbook
chosen
A governance handbook is a comprehensive guide that outlines the structures, roles, processes, and policies by which an organization is directed, controlled, and held accountable.
-
B.
governance doctrine
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 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.
-
D.
governance discipline
Governance discipline is the structured set of principles, processes, and practices used to direct, control, and hold an organization accountable in achieving its objectives and managing risks.
-
E.
corporate governance standard
A corporate governance standard is a formalized set of principles, rules, and best practices that guide how a corporation is directed, controlled, and held accountable to its stakeholders.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10:51 p.m.