Triple
T18015789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SciPy Steering Council |
E430995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source governance council |
C308
|
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 governance council Context triple: [SciPy Steering Council, instanceOf, open-source governance council]
-
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.
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.
-
C.
governing council
chosen
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.
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 advocate
An open-source advocate is a person who actively promotes, supports, and contributes to freely accessible, collaboratively developed software and open standards, emphasizing transparency, community, and shared innovation.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:24 a.m.