Triple
T23923302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Svalbard reindeer |
E602277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subspecies of reindeer |
C48217
|
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 reindeer Context triple: [Svalbard reindeer, instanceOf, subspecies of reindeer]
-
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.
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.
-
C.
subspecies of argali
A subspecies of argali is a distinct population within the argali wild sheep species, differentiated by unique genetic, morphological, or geographic characteristics while remaining capable of interbreeding with other argali subspecies.
-
D.
subspecies of chamois
A subspecies of chamois is a distinct population within the chamois species that exhibits consistent morphological, genetic, or geographical differences while remaining capable of interbreeding with other chamois populations.
-
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. 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 8:41 p.m.