Triple
T29955694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewontin’s paradox of variation |
E760892
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | evolutionary genetics concept |
C25735
|
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: evolutionary genetics concept Context triple: [Lewontin’s paradox of variation, instanceOf, evolutionary genetics concept]
-
A.
framework in evolutionary biology
A framework in evolutionary biology is a conceptual structure that organizes theories, models, and empirical findings to explain how evolutionary processes generate and shape biological diversity over time.
-
B.
population genetics hypothesis
chosen
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.
-
C.
rule in evolutionary biology
A rule in evolutionary biology is a general principle or pattern, often empirically observed rather than strictly law-like, that describes how evolutionary processes tend to shape organisms, populations, or traits over time.
-
D.
rule in speciation genetics
A rule in speciation genetics is a general principle or pattern that describes how genetic differences between populations contribute to the formation and maintenance of new species.
-
E.
subfield of evolutionary biology
A subfield of evolutionary biology is a specialized area of study that focuses on particular aspects of how organisms evolve, such as molecular evolution, population genetics, or evolutionary ecology.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:27 p.m.