Triple
T34756087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moseten–Chon hypothesis |
E1001926
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | proposal of genetic relationship |
C64955
|
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: proposal of genetic relationship Context triple: [Moseten–Chon hypothesis, instanceOf, proposal of genetic relationship]
-
A.
genetic hypothesis
A genetic hypothesis is a testable scientific proposition that explains how specific genes or genetic mechanisms contribute to an observed trait, pattern of inheritance, or biological phenomenon.
-
B.
genetically distinct human populations
Genetically distinct human populations are groups of humans that, due to historical patterns of ancestry, migration, and reproduction, share characteristic frequencies of genetic variants that differ statistically from those of other groups while still belonging to a single interbreeding species.
-
C.
population genetics hypothesis
A population genetics hypothesis is a proposed explanation of how genetic variation is distributed and changes over time within and between populations due to evolutionary forces such as mutation, selection, drift, and migration.
-
D.
relation
A relation is an abstract association that connects two or more entities based on a defined rule, property, or interaction.
-
E.
language-family relationship proposal
chosen
A language-family relationship proposal is a scholarly hypothesis suggesting that two or more language families share a common genetic origin based on comparative linguistic evidence.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
Created at: May 3, 2026, 3:59 p.m.