Triple
T14320400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | fiduciary oversight of Weill Cornell Medical College |
E355069
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governance function |
C11864
|
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 function Context triple: [fiduciary oversight of Weill Cornell Medical College, instanceOf, governance function]
-
A.
governance tool
A governance tool is a system or platform that helps organizations define, implement, monitor, and enforce policies, decision-making processes, and accountability structures to ensure compliant and effective management.
-
B.
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.
-
C.
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.
-
D.
administrative function
chosen
An administrative function is a conceptual class representing tasks and processes that support the organization, coordination, and control of operations within an institution or system.
-
E.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:13 a.m.