Triple
T11100384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenAPI Initiative |
E262485
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open governance consortium |
C999
|
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 consortium Context triple: [OpenAPI Initiative, instanceOf, open governance consortium]
-
A.
open-source organization
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.
public consortium
A public consortium is a collaborative alliance of multiple public or publicly accountable organizations that pool resources, expertise, and governance to pursue shared goals or projects in the public interest.
-
C.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
D.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
E.
multistakeholder organization
chosen
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.