Triple
T26346075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Software Notice and License |
E662779
|
entity |
| Predicate | permitsModificationWithoutContributionBack |
P161281
|
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, permitsModificationWithoutContributionBack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permitsModificationWithoutContributionBack Context triple: [W3C Software Notice and License, permitsModificationWithoutContributionBack, true]
-
A.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
-
B.
notModifiedBy
Indicates that an entity has not been altered, changed, or affected by the specified agent or process.
-
C.
canBeModifiedBetween
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
D.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
E.
canChangeAfter
Indicates that one entity has the ability or permission to alter another entity or its state at some later point in time.
- F. None of above. chosen
Provenance (4 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_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 26, 2026, 10:42 p.m.