Triple
T11655206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Container Initiative |
E276997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open governance project |
C13213
|
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 governance project Context triple: [Open Container Initiative, instanceOf, open governance project]
-
A.
open-source organization
chosen
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
-
B.
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.
-
C.
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.
-
D.
open knowledge program
An open knowledge program is an initiative designed to create, share, and maintain freely accessible, collaboratively developed information resources for public use and learning.
-
E.
Wikimedia governance mechanism
A Wikimedia governance mechanism is a structured process, policy, or body through which the Wikimedia movement makes, implements, and enforces decisions about content, conduct, resources, and organizational direction across its projects and affiliates.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.