Triple
T18528340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHP documentation team |
E452774
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open source community group |
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 group Context triple: [PHP documentation team, instanceOf, open source community group]
-
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 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.
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.
community hub
A community hub is a central place, physical or virtual, where people gather to connect, share resources, collaborate, and participate in activities that support collective well-being and local engagement.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:37 a.m.