Triple
T17675021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elixir Core Team |
E440623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source project core team |
C12274
|
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 core team Context triple: [Elixir Core Team, instanceOf, open source project core team]
-
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 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.
-
C.
open source company
An open source company is a business that develops, maintains, and often monetizes software whose source code is publicly available for use, modification, and distribution under open source licenses.
-
D.
free software project
A free software project is a collaboratively developed software initiative whose source code is openly available and may be used, modified, and redistributed under a license that guarantees these freedoms.
-
E.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10 a.m.