Triple
T3419967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 23andMe |
E72091
|
entity |
| Predicate | usesDataFor |
P98
|
FINISHED |
| Object | genetic research |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: genetic research | Statement: [23andMe, usesDataFor, genetic research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDataFor Context triple: [23andMe, usesDataFor, genetic research]
-
A.
usedDataFrom
Indicates that one entity utilized or relied on data originating from another entity.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
D.
usedDataAnalytics
Indicates that an entity applied data analytics techniques or insights in performing an action or making a decision related to another entity.
-
E.
usesDataStructure
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
- F. None of above.
Provenance (3 batches)
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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94d6808819080997df30119e71e |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:15 p.m.