Triple
T18194862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 20121 |
E435633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sustainable events standard |
C21991
|
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: sustainable events standard Context triple: [ISO 20121, instanceOf, sustainable events standard]
-
A.
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.
-
B.
sustainability certification label
A sustainability certification label is a standardized mark or symbol on products or services indicating they meet defined environmental, social, and/or ethical performance criteria verified by an independent body.
-
C.
sustainability initiative
A sustainability initiative is a coordinated set of actions, policies, and programs designed to reduce environmental impact, conserve resources, and promote long-term ecological, social, and economic well-being.
-
D.
hybrid event management platform
A hybrid event management platform is a unified system that enables planning, hosting, and analyzing events that combine in-person and virtual experiences, including registration, engagement tools, content delivery, and post-event analytics.
-
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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:31 a.m.