Triple
T34579284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPAN Testers |
E887844
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Perl community project |
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: Perl community project Context triple: [CPAN Testers, instanceOf, Perl community project]
-
A.
Haskell infrastructure project
A Haskell infrastructure project is a foundational software system, tooling, or service built in Haskell that supports, automates, or enhances the development, deployment, and operation of other Haskell applications.
-
B.
community development project
A community development project is a coordinated initiative designed to improve the social, economic, and environmental well-being of a specific community through participatory planning and collective action.
-
C.
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.
-
D.
R project hosting service
A R project hosting service is an online platform that provides version control, collaboration tools, and infrastructure for developing, sharing, and maintaining R-based data analysis and software projects.
-
E.
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.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:03 a.m.