Triple
T32709363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Distribution License |
E836355
|
entity |
| Predicate | isSublicensingAllowed |
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: [Eclipse Distribution License, isSublicensingAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSublicensingAllowed Context triple: [Eclipse Distribution License, isSublicensingAllowed, true]
-
A.
allowsSublicensing
chosen
Indicates that one party grants another the right to further license the same rights to additional third parties.
-
B.
hasLicensing
Indicates that one entity holds or is granted licensing rights, permissions, or authorization in relation to another entity or resource.
-
C.
licenseAllows
Indicates that a particular license grants permission for a specified action, use, or access involving an entity.
-
D.
usesLicensingModel
Indicates that one entity employs or applies a particular licensing model in its operations or offerings.
-
E.
coLicensedWith
Indicates that two or more entities share a common license or are authorized under the same licensing agreement.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:10 a.m.