Triple
T24049364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalundborg industrial symbiosis |
E595611
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | eco-industrial network |
C27573
|
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: eco-industrial network Context triple: [Kalundborg industrial symbiosis, instanceOf, eco-industrial network]
-
A.
environmental management network
chosen
An environmental management network is a coordinated system of organizations, stakeholders, and processes that collaboratively monitor, regulate, and improve environmental performance and sustainability across regions or sectors.
-
B.
eco-village
An eco-village is a planned community designed to minimize environmental impact by integrating sustainable housing, renewable energy, local food production, and cooperative social structures.
-
C.
industrial production system
An industrial production system is an organized arrangement of people, machines, materials, methods, and information designed to efficiently transform inputs into standardized goods or services at scale.
-
D.
industrial park
An industrial park is a planned and zoned area of land designated for industrial development, typically providing shared infrastructure, utilities, and transportation access for manufacturing, warehousing, and related businesses.
-
E.
environmental protection system
An environmental protection system is an integrated framework of policies, technologies, and processes designed to monitor, prevent, and mitigate harm to natural ecosystems and human health from environmental hazards and resource exploitation.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
Created at: April 17, 2026, 10:19 p.m.