Triple
T27594059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istio Steering Committee |
E699848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source project committee |
C28850
|
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 committee Context triple: [Istio Steering Committee, instanceOf, open-source project committee]
-
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.
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.
-
C.
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.
-
D.
volunteer committee
chosen
A volunteer committee is a group of individuals who freely offer their time and skills to collaboratively plan, coordinate, and carry out activities or decisions in support of a specific cause, organization, or community need.
-
E.
community development project
A community development project is a coordinated initiative designed to improve the social, economic, and environmental well-being of a specific community through participatory planning and collective action.
- 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.