Triple
T18255773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perl Mongers |
E437219
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Perl community organization |
C20591
|
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: Perl community organization Context triple: [Perl Mongers, instanceOf, Perl community organization]
-
A.
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.
-
B.
community development program
A community development program is an organized initiative designed to improve the social, economic, and environmental well-being of a specific community through collaborative planning, resource mobilization, and capacity-building activities.
-
C.
community organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
D.
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.
-
E.
free software community
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.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:34 a.m.