Triple
T32708415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Foundation Specification License |
E836334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eclipse Foundation license |
C53065
|
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: Eclipse Foundation license Context triple: [Eclipse Foundation Specification License, instanceOf, Eclipse Foundation license]
-
A.
Eclipse project
An Eclipse project is a structured collection of source files, configuration settings, and resources managed within the Eclipse IDE to develop, build, and run software applications.
-
B.
OSI-approved license
An OSI-approved license is a software license that has been reviewed and certified by the Open Source Initiative as complying with its Open Source Definition, ensuring users' rights to freely use, modify, and distribute the software.
-
C.
source-available license
chosen
A source-available license is a software license that allows users to view and sometimes modify the source code but does not meet all the criteria of open-source or free software licenses, often imposing additional restrictions on use, distribution, or modification.
-
D.
OpenJDK distribution
An OpenJDK distribution is a packaged, ready-to-use build of the Open Java Development Kit that includes the Java runtime, development tools, and standard libraries for running and developing Java applications.
-
E.
AROS-specific software license
An AROS-specific software license is a legal framework tailored to the AROS Research Operating System that defines how its source code and binaries may be used, modified, and redistributed.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:10 a.m.