Triple
T29408818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gentoo QA guidelines |
E745840
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Gentoo project policy |
C55568
|
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: Gentoo project policy Context triple: [Gentoo QA guidelines, instanceOf, Gentoo project policy]
-
A.
public policy project
A public policy project is a structured initiative aimed at analyzing, designing, and implementing governmental or institutional policies to address specific societal issues or goals.
-
B.
open source project governance committee
A governance committee for an open source project is a group of stakeholders responsible for setting policies, making strategic decisions, and overseeing the project's direction, community standards, and conflict resolution.
-
C.
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.
-
D.
division of the GNU Project
A division of the GNU Project is an organizational unit within the GNU initiative that focuses on developing, maintaining, or coordinating a specific subset of GNU software, documentation, or related activities.
-
E.
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.
- F. None of above. chosen
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.