Triple
T22375650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPL 1.1 |
E553144
|
entity |
| Predicate | recognizedBy |
P653
|
FINISHED |
| Object | Software Package Data Exchange (SPDX) |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Software Package Data Exchange (SPDX) | Statement: [MPL 1.1, recognizedBy, Software Package Data Exchange (SPDX)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Software Package Data Exchange (SPDX) Context triple: [MPL 1.1, recognizedBy, Software Package Data Exchange (SPDX)]
-
A.
SPDX license list
The SPDX license list is a standardized catalog of commonly used open source software licenses with unique identifiers to support consistent license identification and compliance.
-
B.
OpenSSF
OpenSSF (Open Source Security Foundation) is an industry-wide collaborative initiative focused on improving the security of the open-source software ecosystem through best practices, tooling, and community efforts.
-
C.
Open Packaging Conventions
Open Packaging Conventions is a standardized container and packaging format, best known for underpinning modern Office document file types like .docx, .xlsx, and .pptx by organizing content as structured ZIP-based packages.
-
D.
Common Development and Distribution License
The Common Development and Distribution License (CDDL) is a weak copyleft, file-based open-source software license created by Sun Microsystems and approved by the Open Source Initiative.
-
E.
Python Packaging Authority
The Python Packaging Authority is a working group that oversees and develops key tools, standards, and infrastructure for packaging and distributing Python software.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Software Package Data Exchange (SPDX) Target entity description: Software Package Data Exchange (SPDX) is an open standard for communicating software bill of materials (SBOM) and license information to improve transparency and compliance in software supply chains.
-
A.
SPDX license list
The SPDX license list is a standardized catalog of commonly used open source software licenses with unique identifiers to support consistent license identification and compliance.
-
B.
OpenSSF
OpenSSF (Open Source Security Foundation) is an industry-wide collaborative initiative focused on improving the security of the open-source software ecosystem through best practices, tooling, and community efforts.
-
C.
Open Packaging Conventions
Open Packaging Conventions is a standardized container and packaging format, best known for underpinning modern Office document file types like .docx, .xlsx, and .pptx by organizing content as structured ZIP-based packages.
-
D.
Common Development and Distribution License
The Common Development and Distribution License (CDDL) is a weak copyleft, file-based open-source software license created by Sun Microsystems and approved by the Open Source Initiative.
-
E.
Python Packaging Authority
The Python Packaging Authority is a working group that oversees and develops key tools, standards, and infrastructure for packaging and distributing Python software.
- F. None of above. chosen
Provenance (2 batches)
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. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
Created at: April 16, 2026, 8:45 p.m.