Triple
T27308149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus |
E689124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hominin genus |
C20128
|
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: hominin genus Context triple: [Paranthropus, instanceOf, hominin genus]
-
A.
hominin subtribe
A hominin subtribe is a taxonomic rank below tribe that groups closely related genera of early human ancestors and their relatives based on shared evolutionary traits and lineage.
-
B.
Paranthropus
chosen
Paranthropus is an extinct genus of robust early hominins characterized by heavy chewing adaptations, including large jaws, massive molars, and prominent sagittal crests, that lived in Africa between about 2.7 and 1.0 million years ago.
-
C.
extinct hominin species
An extinct hominin species is a non-living member of the human evolutionary lineage, distinct from modern humans yet sharing common ancestry and exhibiting a combination of primitive and derived traits.
-
D.
Miocene hominoid
A Miocene hominoid is any member of the ape superfamily (Hominoidea) that lived during the Miocene epoch (about 23 to 5 million years ago), representing early stages in the evolution of modern apes and humans.
-
E.
Miocene ape
A Miocene ape is a member of the diverse group of fossil hominoids that lived during the Miocene epoch (about 23–5 million years ago), exhibiting a range of body forms and locomotor adaptations that illuminate early stages of ape and human evolution.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
Created at: April 27, 2026, 11:26 a.m.