Triple
T25133573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conservatoire d’espaces naturels de Bourgogne |
E629594
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservatoire d’espaces naturels |
C8959
|
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: conservatoire d’espaces naturels Context triple: [Conservatoire d’espaces naturels de Bourgogne, instanceOf, conservatoire d’espaces naturels]
-
A.
convention sur la protection de la faune et de la flore
La "convention sur la protection de la faune et de la flore" est un accord international visant à préserver les espèces animales et végétales ainsi que leurs habitats naturels par des mesures de conservation, de réglementation et de coopération entre États.
-
B.
park conservancy
chosen
A park conservancy is a nonprofit or community-based organization dedicated to preserving, maintaining, and enhancing public parks and green spaces through stewardship, fundraising, and advocacy.
-
C.
conservation center
A conservation center is a facility dedicated to protecting, studying, and restoring wildlife, habitats, and natural resources through research, education, and hands-on management.
-
D.
nature reserve
A nature reserve is a protected area of land or water designated to conserve wildlife, habitats, and natural features, often limiting human activities to research, education, and low-impact recreation.
-
E.
conservation district
A conservation district is a designated geographic area where natural resources are managed and protected through coordinated planning, regulation, and community-based conservation practices.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:28 a.m.