Triple
T22375611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPL 1.1 |
E553144
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | version of the Mozilla Public License |
C32048
|
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: version of the Mozilla Public License Context triple: [MPL 1.1, instanceOf, version of the Mozilla Public License]
-
A.
version of the Unicode Standard
A version of the Unicode Standard is a specific, numbered release of the Unicode specification that defines the set of encoded characters, properties, and related algorithms valid at that point in the standard’s evolution.
-
B.
Mozilla project
The Mozilla project is an open-source initiative focused on developing web technologies, applications, and standards that promote an open, accessible, and user-centric internet.
-
C.
family of free software licenses
chosen
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.
standardized license
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.
-
E.
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.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.