Triple
T22498732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EFF Technology Projects |
E556212
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | program of the Electronic Frontier Foundation |
C46399
|
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: program of the Electronic Frontier Foundation Context triple: [EFF Technology Projects, instanceOf, program of the Electronic Frontier Foundation]
-
A.
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.
-
B.
Creative Commons program
A Creative Commons program is an initiative or software tool designed to facilitate the use, creation, and sharing of works under Creative Commons licenses by providing legal, educational, or technical support for open licensing.
-
C.
Mozilla project
The Mozilla project is an open-source initiative focused on developing web technologies, applications, and standards that promote an open, accessible, and user-centric internet.
-
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.
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.
- 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_69e11e5445bc8190b6a9481926db3355 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.