Triple
T27594219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knative Steering Committee |
E699851
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source project governance committee |
C52997
|
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 source project governance committee Context triple: [Knative Steering Committee, instanceOf, open source project governance committee]
-
A.
Python community governance document
A Python community governance document is an official, collaboratively developed text that defines the decision-making structures, roles, processes, and rules by which the Python community organizes and governs itself.
-
B.
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.
-
C.
open source program office
An open source program office is a centralized organizational function that defines policies, provides guidance, and manages processes for the strategic use, contribution to, and governance of open source software within an organization.
-
D.
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.
-
E.
open source contributor
An open source contributor is an individual who voluntarily improves, maintains, or supports publicly available software or documentation by submitting code, reporting issues, reviewing changes, or providing other collaborative input.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 2:06 p.m.