Triple
T26346063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Software Notice and License |
E662779
|
entity |
| Predicate | permitsProprietaryUse |
P16205
|
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: [W3C Software Notice and License, permitsProprietaryUse, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsProprietaryUse Context triple: [W3C Software Notice and License, permitsProprietaryUse, true]
-
A.
allowsProprietaryDerivativeWorks
chosen
Indicates that one party grants permission for others to create and distribute derivative works that may be kept proprietary rather than shared under the same open terms.
-
B.
permitsCommercialUse
Indicates that an entity grants permission for its use in commercial or profit-generating contexts.
-
C.
allowsPatentUse
Indicates that one entity grants another entity permission to use a patented invention under specified terms or conditions.
-
D.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
-
E.
hasProprietaryStatus
Indicates that something is owned, controlled, or protected as proprietary rather than being public or freely available.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa718188190a3f4d76db2cdf670 |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:42 p.m.