Triple
T12309058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSFLA |
E293428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional branch of the Free Software Foundation |
C13213
|
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: regional branch of the Free Software Foundation Context triple: [FSFLA, instanceOf, regional branch of the Free Software Foundation]
-
A.
open-source organization
chosen
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
-
B.
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.
-
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.
free software community
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.
-
E.
free software advocacy project
A free software advocacy project is an organized effort that promotes the use, development, and protection of software that respects users’ freedom to run, study, modify, and share it.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.