Triple
T22322525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zope Public License |
E551821
|
entity |
| Predicate | permitsSublicensing |
P20010
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
How this triple was built (2 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: true | Statement: [Zope Public License, permitsSublicensing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsSublicensing Context triple: [Zope Public License, permitsSublicensing, true]
-
A.
allowsSublicensing
chosen
Indicates that one party grants another the right to further license the same rights to additional third parties.
-
B.
licensingRestriction
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
C.
canBeLicensedUnder
Indicates that something is eligible or suitable to be granted a particular legal license or licensing terms.
-
D.
licensingBasisIncludes
Indicates that one licensing basis incorporates or contains another licensing basis as part of its governing conditions or requirements.
-
E.
requiresSameLicenseOnDerivatives
Indicates that any derivative works must be distributed under the same license as the original work.
- F. None of above.
Provenance (3 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15765a004819081dcdccbfd0efea7 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:42 p.m.