Triple
T13244114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Conservation Division |
E315353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | conservation agency |
C18822
|
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: conservation agency Context triple: [Lexington Conservation Division, instanceOf, conservation agency]
-
A.
conservation department
chosen
A conservation department is an organizational unit responsible for protecting, managing, and restoring natural resources, ecosystems, and biodiversity within a defined jurisdiction or scope.
-
B.
fish and wildlife agency
A fish and wildlife agency is a governmental or tribal organization responsible for conserving, managing, and regulating fish, wildlife, and their habitats for ecological health and public benefit.
-
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 conservation organisation
A nature conservation organisation is an entity dedicated to protecting, restoring, and sustainably managing natural environments and biodiversity through research, advocacy, education, and on-the-ground conservation actions.
-
E.
natural resources management agency
A natural resources management agency is an organization responsible for planning, regulating, and overseeing the sustainable use, conservation, and restoration of natural resources such as land, water, forests, wildlife, and minerals.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:23 p.m.