Triple
T21742145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nominating and Corporate Governance Committee of Twitter, Inc. |
E536683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nominating and governance committee |
C4031
|
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: nominating and governance committee Context triple: [Nominating and Corporate Governance Committee of Twitter, Inc., instanceOf, nominating and governance committee]
-
A.
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.
-
B.
board committee
chosen
A board committee is a small, specialized group of board members delegated specific responsibilities to support the board’s governance, oversight, and decision-making functions.
-
C.
public accounts committee
A public accounts committee is a legislative body responsible for examining government expenditures to ensure they are lawful, efficient, and in line with approved budgets, thereby promoting transparency and accountability in public finance.
-
D.
compliance committee
A compliance committee is a designated group within an organization responsible for overseeing, monitoring, and guiding adherence to legal, regulatory, and internal policy requirements.
-
E.
senior committee
A senior committee is a group of high-ranking or experienced individuals formally convened to provide oversight, strategic guidance, and key decisions on significant organizational matters.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:49 p.m.