Triple
T35197341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Data.gov |
E1016298
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open government initiative |
C8485
|
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 government initiative Context triple: [Data.gov, instanceOf, open government initiative]
-
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.
government transparency initiative
chosen
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.
-
C.
open data policy instrument
An open data policy instrument is a formal mechanism—such as laws, regulations, guidelines, or standards—used by governments or organizations to mandate, enable, or incentivize the release and reuse of data in open, accessible formats.
-
D.
open data advocate
An open data advocate is a person who promotes the free, accessible, and transparent sharing of data for public use, innovation, and accountability.
-
E.
data-driven government program
A data-driven government program is an initiative that systematically collects, analyzes, and applies data to design, implement, and continuously improve public policies and services for better outcomes and accountability.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.