Triple
T31347824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Party Planning Committee |
E799498
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | workplace committee |
C6579
|
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: workplace committee Context triple: [Party Planning Committee, instanceOf, workplace committee]
-
A.
labor relations committee
A labor relations committee is a group within an organization responsible for facilitating communication, negotiation, and conflict resolution between management and employees regarding workplace conditions, rights, and policies.
-
B.
conference committee
A conference committee is a group of individuals responsible for planning, organizing, and overseeing the academic, logistical, and promotional aspects of a conference.
-
C.
professional organization committee
chosen
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.
-
D.
college committee
A college committee is a formally organized group within a college composed of faculty, staff, and sometimes students, tasked with deliberating on specific academic or administrative issues and making recommendations or decisions to support institutional governance and operations.
-
E.
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.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:17 p.m.