Triple
T22236650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE corporate governance |
E549609
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizational governance structure |
C38265
|
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 structure Context triple: [IEEE corporate governance, instanceOf, organizational governance structure]
-
A.
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.
-
B.
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.
-
C.
corporate governance standard
chosen
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.
-
D.
organizational model
An organizational model is a conceptual framework that defines how an organization’s structure, roles, processes, and relationships are arranged to achieve its goals and coordinate activities.
-
E.
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.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:38 p.m.