Triple
T26316530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personal Genome Project |
E661987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open science project |
C120
|
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: open science project Context triple: [Personal Genome Project, instanceOf, open science project]
-
A.
open science policy
Open science policy is a set of principles and guidelines that promote transparent, accessible, and collaborative research practices, including open access to publications, data, methods, and educational resources.
-
B.
research project
chosen
A research project is a structured, systematic investigation designed to answer specific questions or test hypotheses by collecting, analyzing, and interpreting data within a defined scope and timeframe.
-
C.
historical scientific project
A historical scientific project is a past, organized effort to investigate specific scientific questions or develop technologies, whose context, methods, and outcomes are studied to understand the evolution of scientific knowledge and practice.
-
D.
open data initiative
An open data initiative is a coordinated effort, typically by governments or organizations, to make datasets freely available, accessible, and reusable by the public to promote transparency, innovation, and informed decision-making.
-
E.
citizen science initiative
A citizen science initiative is a collaborative project that engages members of the public in scientific research activities—such as data collection, analysis, or problem-solving—to advance knowledge and address real-world issues.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:25 p.m.