Triple
T28020797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Protection Committee |
E707681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental advisory committee |
C13655
|
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: environmental advisory committee Context triple: [Environmental Protection Committee, instanceOf, environmental advisory committee]
-
A.
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.
-
B.
health advisory council
A health advisory council is a group of experts and stakeholders that provides guidance, recommendations, and oversight on public health policies, programs, and initiatives.
-
C.
environmental protection unit
An environmental protection unit is an organized group or division dedicated to monitoring, preserving, and improving the natural environment by enforcing regulations, mitigating pollution, and promoting sustainable practices.
-
D.
environmental organisation
chosen
An environmental organisation is a group dedicated to protecting, preserving, and improving the natural environment through advocacy, conservation, education, and policy influence.
-
E.
environmental science organisation
An environmental science organisation is an entity that conducts research, monitoring, and advocacy to understand environmental systems and promote the protection and sustainable management of natural resources.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 8:09 p.m.