Triple
T30315093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APSL 1.0 |
E771038
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Apple Public Source License version |
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: Apple Public Source License version Context triple: [APSL 1.0, instanceOf, Apple Public Source License version]
-
A.
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.
-
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.
family of free software licenses
A family of free software licenses is a group of related legal frameworks that grant users the freedom to use, study, modify, and redistribute software, often with varying conditions on how derivative works are shared.
-
D.
Apple policy document
An Apple policy document is an official written record that defines Apple’s rules, standards, and procedures governing specific activities, behaviors, or decisions within its ecosystem.
-
E.
Apple developer initiative
Apple developer initiative is a program or effort led by Apple to support, engage, and empower software developers through tools, resources, education, and community-building around Apple platforms.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:51 p.m.