Triple
T32709361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Distribution License |
E836355
|
entity |
| Predicate | isModificationAllowed |
P174827
|
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: [Eclipse Distribution License, isModificationAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModificationAllowed Context triple: [Eclipse Distribution License, isModificationAllowed, true]
-
A.
isMutable
Indicates that an entity can be changed or modified after it has been created or initially defined.
-
B.
isEditableIn
Indicates that an entity can be modified or changed within a specified context, environment, or container.
-
C.
isEditableByUser
Indicates that a given item or resource can be modified or updated by a specified user.
-
D.
canBeModifiedBetween
Indicates that something is allowed or able to be changed during a specified interval or between defined points or states.
-
E.
mayBeModifiedBy
Indicates that an entity has the potential to be altered, changed, or updated by another entity or process.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c87bf9c481908804bd231d60cd30 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.