Triple
T17560098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeBSD Core Team |
E427675
|
entity |
| Predicate | governs |
P760
|
FINISHED |
| Object | FreeBSD project governance rules |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: FreeBSD project governance rules | Statement: [FreeBSD Core Team, governs, FreeBSD project governance rules]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FreeBSD project governance rules Context triple: [FreeBSD Core Team, governs, FreeBSD project governance rules]
-
A.
Gentoo project policies
Gentoo project policies are the formal rules and guidelines that define how the Gentoo Linux distribution and its community are managed, developed, and organized.
-
B.
FreeBSD Core Team
The FreeBSD Core Team is the elected leadership body responsible for overseeing the development, direction, and policies of the FreeBSD operating system project.
-
C.
Debian Free Software Guidelines
The Debian Free Software Guidelines are a set of principles that define what constitutes free and open-source software for inclusion in the Debian operating system and have influenced other licensing and open-source definitions.
-
D.
Debian Constitution
The Debian Constitution is the formal document that defines the organizational structure, decision-making processes, and powers of the various bodies within the Debian Project.
-
E.
Mozilla community governance
Mozilla community governance is the collaborative decision-making and leadership framework that guides how the global Mozilla community organizes its work, sets priorities, and upholds its open-source and internet-health values.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: FreeBSD project governance rules Target entity description: The FreeBSD project governance rules are the formal policies and procedures that define how the FreeBSD open-source operating system project is organized, managed, and decision-making authority is exercised.
-
A.
Gentoo project policies
Gentoo project policies are the formal rules and guidelines that define how the Gentoo Linux distribution and its community are managed, developed, and organized.
-
B.
FreeBSD Core Team
chosen
The FreeBSD Core Team is the elected leadership body responsible for overseeing the development, direction, and policies of the FreeBSD operating system project.
-
C.
Debian Free Software Guidelines
The Debian Free Software Guidelines are a set of principles that define what constitutes free and open-source software for inclusion in the Debian operating system and have influenced other licensing and open-source definitions.
-
D.
Debian Constitution
The Debian Constitution is the formal document that defines the organizational structure, decision-making processes, and powers of the various bodies within the Debian Project.
-
E.
Mozilla community governance
Mozilla community governance is the collaborative decision-making and leadership framework that guides how the global Mozilla community organizes its work, sets priorities, and upholds its open-source and internet-health values.
- F. None of above.
Provenance (2 batches)
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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
Created at: April 10, 2026, 5:50 a.m.