Triple
T27637100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redis Source Available License |
E696498
|
entity |
| Predicate | hasRestrictionType |
P64496
|
FINISHED |
| Object | cloud service restriction |
—
|
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: cloud service restriction | Statement: [Redis Source Available License, hasRestrictionType, cloud service restriction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRestrictionType Context triple: [Redis Source Available License, hasRestrictionType, cloud service restriction]
-
A.
hasTypeOfRestriction
chosen
Indicates that an entity is subject to a specific kind or category of restriction that limits its use, access, or behavior.
-
B.
hasHumanUseRestriction
Indicates that there is a limitation or condition on how something may be used by humans.
-
C.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
-
D.
hasMoreRestrictionsThan
Indicates that one entity is subject to a greater number or stricter set of limitations, rules, or constraints than another entity.
-
E.
hasProgramTypeRestriction
Indicates that there is a constraint limiting which types of programs are allowed or applicable in a given 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fee0b2da3c8190a3519d0564f2f32d |
completed | May 9, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69fee05b315c819081dfcbfb15273487 |
completed | May 9, 2026, 7:20 a.m. |
Created at: April 27, 2026, 2:24 p.m.