Triple
T4552304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hardy–Weinberg principle |
E120393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in genetics |
C17163
|
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: theorem in genetics Context triple: [Hardy–Weinberg principle, instanceOf, theorem in genetics]
-
A.
mathematical theorem
A mathematical theorem is a rigorously proven statement derived from axioms and previously established results, expressing a fundamental truth within a formal mathematical system.
-
B.
subfield of genetics
A subfield of genetics is a specialized branch that focuses on a particular aspect of heredity and gene function, such as molecular mechanisms, population patterns, or the genetic basis of specific traits or diseases.
-
C.
geneticist
A geneticist is a scientist who studies genes, heredity, and genetic variation in organisms to understand how traits are passed on and how they influence health and development.
-
D.
result in probability theory
In probability theory, a result is a formally stated and proven fact—such as a theorem, lemma, or corollary—that describes a property or relationship involving probabilistic concepts like random variables, events, or distributions.
-
E.
qualitative rule in gene regulatory network theory
A qualitative rule in gene regulatory network theory is a logical, often discrete, relationship that specifies how the activity state of one or more genes or regulatory elements determines the activation, repression, or maintenance of another gene’s expression without relying on precise quantitative parameters.
- F. None of above. chosen
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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
Created at: March 20, 2026, 1:09 p.m.