Triple
T17519357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Encode OSS |
E426646
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source software organization |
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: open-source software organization Context triple: [Encode OSS, instanceOf, open-source software organization]
-
A.
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.
-
B.
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.
-
C.
open-source software advocate
An open-source software advocate is a person who actively promotes the use, development, and principles of open-source software, emphasizing transparency, collaboration, and community-driven innovation.
-
D.
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.
-
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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:49 a.m.