Triple
T11100087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperledger |
E262479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | open-source collaborative project |
C12274
|
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 collaborative project Context triple: [Hyperledger, instanceOf, open-source collaborative project]
-
A.
collaborative project
chosen
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
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.
open-source organization
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.
-
D.
open source contributor
An open source contributor is an individual who voluntarily improves, maintains, or supports publicly available software or documentation by submitting code, reporting issues, reviewing changes, or providing other collaborative input.
-
E.
open-source framework
An open-source framework is a publicly accessible, collaboratively developed software foundation that provides reusable components and tools to simplify and accelerate application development.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.