Triple
T29986491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | open science movement |
E761748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research transparency initiative |
C39954
|
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: research transparency initiative Context triple: [open science movement, instanceOf, research transparency initiative]
-
A.
government transparency initiative
A government transparency initiative is a coordinated effort by public institutions to proactively disclose information, decisions, and processes in accessible formats to enhance accountability, public trust, and citizen participation.
-
B.
research initiative
A research initiative is a coordinated, goal-driven effort to investigate specific questions or problems, typically organized around a defined scope, methodology, timeline, and set of expected outcomes.
-
C.
meta-science project
chosen
A meta-science project is an initiative that systematically studies and improves scientific practices, methods, and structures to enhance the reliability, efficiency, and impact of research.
-
D.
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.
-
E.
research project
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.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:36 p.m.