Triple
T26576360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana black bear |
E666957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subspecies of American black bear |
C51784
|
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: subspecies of American black bear Context triple: [Louisiana black bear, instanceOf, subspecies of American black bear]
-
A.
subspecies of brown bear
A subspecies of brown bear is a distinct population within the brown bear species that exhibits consistent genetic, morphological, or geographic differences from other brown bear populations while remaining capable of interbreeding with them.
-
B.
subspecies of gray wolf
A subspecies of gray wolf is a distinct population within the gray wolf species that exhibits consistent genetic, morphological, and/or behavioral differences adapted to a particular geographic region.
-
C.
subspecies of red fox
A subspecies of red fox is a geographically or genetically distinct population within the red fox species that exhibits consistent morphological, behavioral, or genetic differences while remaining capable of interbreeding with other red fox populations.
-
D.
wildcat subspecies
A wildcat subspecies is a distinct population within the wildcat species that exhibits unique genetic, morphological, and behavioral traits adapted to a specific geographic region.
-
E.
subspecies of brow-antlered deer
A subspecies of brow-antlered deer is a distinct population within the species that exhibits consistent genetic, morphological, or behavioral differences and typically occupies a specific geographic range.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2 a.m.