Triple
T22286106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chesapeake Bay blue crabs |
E550865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | culturally significant species |
C46056
|
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: culturally significant species Context triple: [Chesapeake Bay blue crabs, instanceOf, culturally significant species]
-
A.
species of conservation concern
A species of conservation concern is a plant or animal whose population status, trends, or threats indicate it may be at risk and therefore warrants special management, monitoring, or protection efforts.
-
B.
endangered species
An endangered species is a type of organism whose population has declined to a critically low level, placing it at high risk of extinction in the near future.
-
C.
international species protection list
An international species protection list is an officially recognized catalog of plant and animal species that are afforded special legal or conservation status across multiple countries to prevent their decline or extinction.
-
D.
natural heritage collection
A natural heritage collection is an organized assemblage of preserved natural specimens, associated data, and documentation that represent and safeguard the biodiversity, geology, and ecosystems of a region or the planet for research, education, and conservation.
-
E.
conservation status
Conservation status is a classification that indicates the likelihood that a species or ecosystem will remain extant in the near future, based on factors such as population trends, threats, and habitat conditions.
- F. None of above. chosen
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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:40 p.m.