Triple
T32709360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse Distribution License |
E836355
|
entity |
| Predicate | isCommercialUseAllowed |
P131099
|
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, isCommercialUseAllowed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommercialUseAllowed Context triple: [Eclipse Distribution License, isCommercialUseAllowed, true]
-
A.
permitsCommercialUse
chosen
Indicates that an entity grants permission for its use in commercial or profit-generating contexts.
-
B.
isNonCommercial
Indicates that the associated entity, use, or activity is not intended for or involved in commercial, profit-generating purposes.
-
C.
hasCommercialFunction
Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
-
D.
hasCommercialAppeal
Indicates that something possesses qualities likely to attract buyers or generate profitable market interest.
-
E.
usesForCommercialShipping
Indicates that something is employed as a means or method for transporting goods in a commercial or business context.
- 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_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:10 a.m.