Triple
T32708413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Foundation Specification License |
E836334
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | software specification license |
C248
|
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: software specification license Context triple: [Eclipse Foundation Specification License, instanceOf, software specification license]
-
A.
standardized license
chosen
A standardized license is a pre-defined, widely accepted legal agreement that sets uniform terms and conditions for using, sharing, or distributing a product, service, or intellectual property.
-
B.
proprietary license
A proprietary license is a legal agreement that grants users limited rights to use, but not freely modify or redistribute, software or other intellectual property owned and controlled by a specific individual or organization.
-
C.
specification
A specification is a detailed, precise description of requirements, behaviors, and constraints that a system, component, or process must satisfy.
-
D.
custom license
A custom license is a tailored legal agreement that defines specific permissions, restrictions, and conditions for using, modifying, and distributing a particular work or resource.
-
E.
software documentation
Software documentation is the organized collection of written materials that explains a software system’s purpose, design, functionality, and usage for developers, users, and other stakeholders.
- 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.