Triple
T26364365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sitka black-tailed deer |
E660293
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subspecies of deer |
C26832
|
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 deer Context triple: [Sitka black-tailed deer, instanceOf, subspecies of deer]
-
A.
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.
-
B.
subspecies of reindeer
A subspecies of reindeer is a distinct population within the reindeer species that exhibits consistent genetic, morphological, or behavioral differences and typically occupies a specific geographic range.
-
C.
moose subspecies
A moose subspecies is a regional population of moose distinguished from other moose groups by consistent differences in physical characteristics, genetics, and geographic distribution.
-
D.
subspecies of mammal
chosen
A subspecies of mammal is a taxonomic rank below species that represents a distinct, interbreeding population with consistent morphological, genetic, or behavioral differences from other populations of the same species, yet still capable of producing fertile offspring with them.
-
E.
subspecies of mountain zebra
A subspecies of mountain zebra is a distinct population within the mountain zebra species, characterized by unique genetic, morphological, or geographic traits that differentiate it from other mountain zebra populations.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:54 p.m.