Triple
T22931942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GTR Tests database |
E569465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | genetic test database |
C24488
|
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: genetic test database Context triple: [GTR Tests database, instanceOf, genetic test database]
-
A.
direct-to-consumer DNA testing company
A direct-to-consumer DNA testing company provides genetic testing services directly to individuals, typically via mail-in saliva kits, and delivers personalized reports on ancestry, health risks, traits, or wellness without requiring a healthcare provider intermediary.
-
B.
ancestry DNA test
An ancestry DNA test is a genetic analysis service that examines a person's DNA to estimate their ethnic origins, identify ancestral regions, and potentially connect them with genetic relatives.
-
C.
genetic variant
A genetic variant is a difference in the DNA sequence among individuals or between a given sequence and a reference genome, which may or may not affect biological function or traits.
-
D.
genetics research center
A genetics research center is a specialized facility where scientists study genes, heredity, and molecular biology to advance understanding of genetic mechanisms and develop applications in medicine, agriculture, and biotechnology.
-
E.
biological database
chosen
A biological database is an organized, searchable repository that stores, manages, and provides access to biological information such as sequences, structures, functions, and interactions of biomolecules and organisms.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:44 p.m.