Triple
T28676716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haldane’s cost of selection |
E725887
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | population 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: population genetics concept Context triple: [Haldane’s cost of selection, instanceOf, population genetics concept]
-
A.
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.
-
B.
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.
-
C.
theorem in genetics
A theorem in genetics is a formally proven statement that describes a fundamental, generalizable relationship or principle governing the inheritance, variation, or behavior of genetic material.
-
D.
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.
-
E.
population dynamics model
A population dynamics model is a mathematical or computational framework that describes how the size and structure of a population change over time under the influence of births, deaths, migration, and interactions with the environment or other populations.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 5:06 a.m.