Triple
T8391025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governance Committee of the Board of Trustees of the Wikimedia Foundation |
E197942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 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: governance committee Context triple: [Governance Committee of the Board of Trustees of the Wikimedia Foundation, instanceOf, 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.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
D.
governing body subcommittee
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
-
E.
rule‑making committee
A rule‑making committee is a group formally tasked with developing, reviewing, and approving rules or regulations that govern the behavior, procedures, or operations of an organization or system.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 6:03 p.m.