Triple
T5835789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sumatran elephant |
E129465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subspecies of Asian elephant |
C18968
|
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 Asian elephant Context triple: [Sumatran elephant, instanceOf, subspecies of Asian elephant]
-
A.
tiger subspecies
A tiger subspecies is a distinct population of tigers within the species Panthera tigris, characterized by unique genetic, morphological, and geographic traits that differentiate it from other tiger groups.
-
B.
elk subspecies
An elk subspecies is a distinct population within the elk species characterized by unique genetic, morphological, and behavioral traits adapted to specific geographic regions.
-
C.
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.
-
D.
leopard subspecies
A leopard subspecies is a distinct population of leopards within the species Panthera pardus, characterized by unique genetic, morphological, and geographic traits that differentiate it from other leopard populations.
-
E.
bird subspecies
A bird subspecies is a distinct population within a bird species that shows consistent genetic, morphological, or behavioral differences and occupies a specific geographic range, but can still interbreed with other populations of the same species.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:54 p.m.