Triple
T18976170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 14090 |
E464301
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | climate change adaptation standard |
C36881
|
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: climate change adaptation standard Context triple: [ISO 14090, instanceOf, climate change adaptation standard]
-
A.
climate services framework
A climate services framework is a structured approach that connects climate data, tools, and expertise with user needs to support informed decision-making and climate-resilient planning across sectors.
-
B.
agricultural standard
An agricultural standard is an agreed-upon set of criteria, specifications, and practices that define quality, safety, and production methods for agricultural products and processes.
-
C.
resilience management framework
chosen
A resilience management framework is a structured approach that integrates policies, processes, and tools to anticipate, absorb, adapt to, and recover from disruptions while maintaining essential functions and enabling continuous improvement.
-
D.
hospitality-specific LEED adaptation
A hospitality-specific LEED adaptation is a tailored version of the LEED green building rating system that addresses the unique operational, design, and guest-experience requirements of hotels and other lodging facilities.
-
E.
standardized climate modeling input
A standardized climate modeling input is a consistently formatted, quality-controlled dataset or parameter set designed to ensure comparability, reproducibility, and interoperability across different climate models and simulations.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, noon