Triple
T26818315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | multiregional evolution debate |
E675176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | paleoanthropological controversy |
C5012
|
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: paleoanthropological controversy Context triple: [multiregional evolution debate, instanceOf, paleoanthropological controversy]
-
A.
paleoanthropological site
A paleoanthropological site is a location where physical evidence of ancient humans and their ancestors—such as fossils, artifacts, and environmental remains—is preserved and studied to understand human evolution.
-
B.
scientific controversy
chosen
A scientific controversy is a sustained public or professional disagreement among scientists over the interpretation of evidence, validity of methods, or implications of findings within a particular field of research.
-
C.
prehistoric human
A prehistoric human is an early member of the Homo genus who lived before the advent of written records, characterized by the use of simple tools, hunter-gatherer lifestyles, and gradual cognitive and cultural development.
-
D.
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.
-
E.
paleontological work
A paleontological work is a scholarly or scientific product—such as a paper, monograph, report, or curated dataset—that documents, analyzes, or interprets fossil evidence to reconstruct past life and ancient environments.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 4:53 a.m.