Triple
T29407430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedora Packaging Committee |
E745807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fedora Project body |
C24724
|
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: Fedora Project body Context triple: [Fedora Packaging Committee, instanceOf, Fedora Project body]
-
A.
Fedora project
chosen
The Fedora Project is a community-driven open source initiative that develops the Fedora Linux distribution and related technologies, focusing on innovation, freedom, and collaboration.
-
B.
Debian project body
The Debian project body is the collective organizational entity responsible for coordinating development, governance, and maintenance of the Debian operating system and its associated community processes.
-
C.
Debian Project document
A Debian Project document is an official or semi-official written artifact produced within the Debian community that records policies, procedures, decisions, or technical information relevant to the development, governance, or use of the Debian operating system.
-
D.
Debian Project role
A Debian Project role represents a specific set of responsibilities, permissions, and activities undertaken by an individual or group to contribute to the development, maintenance, and governance of the Debian operating system.
-
E.
FreeBSD project entity
A FreeBSD project entity represents an organized initiative, subproject, or working group within the FreeBSD ecosystem that coordinates resources, contributors, and activities toward specific technical or community goals.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:55 p.m.