Triple
T19814572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lok Sabha Business Advisory Committee (by convention) |
E476027
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | business advisory committee |
C655
|
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: business advisory committee Context triple: [Lok Sabha Business Advisory Committee (by convention), instanceOf, business advisory committee]
-
A.
advisory body
chosen
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
-
B.
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.
-
C.
business consortium
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
-
D.
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.
-
E.
municipal advisory committee
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:50 p.m.