Triple
T20803453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waste Management, Inc. |
E512096
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental services company |
C43775
|
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 services company Context triple: [Waste Management, Inc., instanceOf, environmental services company]
-
A.
environmental consulting division
The environmental consulting division provides expert analysis, guidance, and solutions to help organizations assess, manage, and reduce their environmental impacts while ensuring regulatory compliance and sustainability.
-
B.
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.
-
C.
oil and gas services company
An oil and gas services company provides specialized technical, operational, and logistical support to exploration and production firms across the hydrocarbon value chain.
-
D.
sustainable urban development company
A sustainable urban development company plans, designs, and builds city spaces and infrastructure that minimize environmental impact, promote social equity, and support long-term economic resilience.
-
E.
environmental partnership
An environmental partnership is a collaborative relationship between organizations, communities, or stakeholders formed to jointly plan and implement actions that protect, restore, or sustainably manage natural resources and ecosystems.
- F. None of above. chosen
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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:39 p.m.