Triple
T13225517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee Management Secretariat of the General Services Administration |
E314870
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | committee management office |
C14661
|
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: committee management office Context triple: [Committee Management Secretariat of the General Services Administration, instanceOf, committee management office]
-
A.
organizational committee
An organizational committee is a structured group of individuals formally appointed within an organization to plan, coordinate, and oversee specific functions, projects, or decision-making processes.
-
B.
professional organization committee
A professional organization committee is a structured group of members within a professional body tasked with planning, overseeing, and executing specific functions or initiatives to support the organization’s goals and its stakeholders.
-
C.
board committee
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.
-
D.
coordination office
chosen
A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
-
E.
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.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:19 p.m.