Triple
T27637102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redis Source Available License |
E696498
|
entity |
| Predicate | licenseGrant |
P181
|
FINISHED |
| Object | non-exclusive |
—
|
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: non-exclusive | Statement: [Redis Source Available License, licenseGrant, non-exclusive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseGrant Context triple: [Redis Source Available License, licenseGrant, non-exclusive]
-
A.
license
chosen
Indicates that one entity has granted another entity formal permission or authorization to use, perform, or exploit something under specified terms.
-
B.
licenseFor
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
C.
licenseAuthor
Indicates that one entity is the author or originator of a license granted to another entity.
-
D.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
E.
licenseModel
Indicates the licensing scheme or framework that governs how something may be used, distributed, or accessed.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:24 p.m.