Triple
T10827761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Lab |
E255537
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source community |
C8513
|
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 community Context triple: [Public Lab, instanceOf, open-source community]
-
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.
free software community
chosen
A free software community is a collaborative group of users and developers who create, share, and improve software whose source code is openly available and can be freely used, modified, and redistributed.
-
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.
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.
-
E.
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.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.