Triple
T33489252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSI Directive |
E857695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open data policy instrument |
C60959
|
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 data policy instrument Context triple: [PSI Directive, instanceOf, open data policy instrument]
-
A.
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.
-
B.
open data license
An open data license is a legal framework that grants users permission to freely access, use, modify, and share data, typically under conditions such as attribution and share-alike.
-
C.
open educational resources policy instrument
An open educational resources policy instrument is a formal mechanism—such as laws, regulations, funding schemes, or institutional guidelines—designed to encourage, mandate, or support the creation, adoption, and sharing of openly licensed educational materials.
-
D.
open data index
An open data index is a systematic ranking or assessment framework that evaluates and compares the availability, accessibility, quality, and usability of open government or institutional data across different entities or jurisdictions.
-
E.
open data platform
An open data platform is a system that collects, manages, and publishes structured datasets with standardized formats and open access policies, enabling users to discover, download, and reuse data freely.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:38 a.m.