Triple
T29390901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limor Fried |
E745366
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source hardware advocate |
C3673
|
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: open-source hardware advocate Context triple: [Limor Fried, instanceOf, open-source hardware advocate]
-
A.
open-source advocate
chosen
An open-source advocate is a person who actively promotes, supports, and contributes to freely accessible, collaboratively developed software and open standards, emphasizing transparency, community, and shared innovation.
-
B.
open-source hardware company
An open-source hardware company designs, develops, and sells physical products whose schematics, designs, and source files are publicly shared, allowing anyone to study, modify, and reproduce the hardware.
-
C.
open-source software advocate
An open-source software advocate is a person who actively promotes the use, development, and principles of open-source software, emphasizing transparency, collaboration, and community-driven innovation.
-
D.
open hardware ecosystem
An open hardware ecosystem is a collaborative environment in which hardware designs, tools, and documentation are freely shared, modified, and redistributed by a community to accelerate innovation and reduce barriers to physical technology development.
-
E.
open hardware project
An open hardware project is a collaborative initiative to design, document, and share physical devices whose schematics, source files, and build instructions are publicly available for anyone to study, modify, and reproduce.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:42 p.m.