Triple
T4616569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 14000 family |
E100882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | environmental management standard |
C1116
|
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 management standard Context triple: [ISO 14000 family, instanceOf, environmental management standard]
-
A.
environmental management division
The environmental management division is an organizational unit responsible for planning, implementing, and overseeing policies and programs that protect the environment, ensure regulatory compliance, and promote sustainable use of natural resources.
-
B.
sustainability certification body
An organization that develops, manages, and enforces standards to assess and certify the environmental, social, and economic sustainability performance of products, services, or entities.
-
C.
environmental governance instrument
chosen
An environmental governance instrument is a policy tool, mechanism, or institutional arrangement used by public or private actors to influence behaviors and decisions in order to protect, manage, or restore the environment.
-
D.
environmental programme
An environmental programme is an organized set of coordinated activities, policies, and initiatives designed to protect, manage, or improve the natural environment and promote sustainable practices.
-
E.
environmental sustainability goal
An environmental sustainability goal is a specific, measurable objective aimed at preserving or improving natural ecosystems and resources while minimizing negative human impact on the environment over time.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.