Triple
T27593144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNCF Technical Oversight Committee |
E699827
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CNCF governing body |
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: CNCF governing body Context triple: [CNCF Technical Oversight Committee, instanceOf, CNCF governing body]
-
A.
Linux Foundation project
A Linux Foundation project is a collaborative, open-source initiative hosted under the Linux Foundation that develops and maintains software, standards, or infrastructure for the broader technology ecosystem.
-
B.
cybersecurity coordination body
A cybersecurity coordination body is an organization that facilitates collaboration, information sharing, and joint response among stakeholders to prevent, detect, and mitigate cyber threats.
-
C.
ARIN organizational body
An ARIN organizational body is a formal entity recognized by the American Registry for Internet Numbers that participates in the governance, policy development, and administration of Internet number resources within the ARIN service region.
-
D.
governance network
A governance network is a structured system of interconnected actors—such as governments, organizations, and communities—who collaboratively make, implement, and oversee rules and decisions to guide collective behavior and outcomes.
-
E.
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.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.