Triple
T29661170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Facilities Committee |
E750408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing board 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: governing board committee Context triple: [Facilities Committee, instanceOf, governing board committee]
-
A.
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.
-
B.
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.
-
C.
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.
-
D.
board of trustees
A board of trustees is a governing body of individuals legally entrusted with overseeing an organization’s mission, assets, and strategic direction on behalf of its stakeholders or beneficiaries.
-
E.
committee of a university board of trustees
A committee of a university board of trustees is a formally designated subgroup of trustees charged with focusing on specific governance areas—such as finance, academic affairs, or facilities—and making recommendations or decisions within its defined scope of authority.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 6:58 p.m.