Triple
T17560072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FreeBSD Core Team |
E427675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FreeBSD project entity |
C39334
|
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: FreeBSD project entity Context triple: [FreeBSD Core Team, instanceOf, FreeBSD project entity]
-
A.
Fedora project
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.
free software project
A free software project is a collaboratively developed software initiative whose source code is openly available and may be used, modified, and redistributed under a license that guarantees these freedoms.
-
C.
Linux Foundation project
A Linux Foundation project is a collaborative, open-source initiative hosted under the Linux Foundation that develops and maintains software, standards, or infrastructure for the broader technology ecosystem.
-
D.
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.
-
E.
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.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.