Triple
T32490981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denys Vlasenko |
E830383
|
entity |
| Predicate | licenseWork |
P146942
|
FINISHED |
| Object | GPL-licensed software |
—
|
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: GPL-licensed software | Statement: [Denys Vlasenko, licenseWork, GPL-licensed software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licenseWork Context triple: [Denys Vlasenko, licenseWork, GPL-licensed software]
-
A.
licensesWorksBy
chosen
Indicates that one entity grants legal permission for the use or exploitation of works created by another entity.
-
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.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
D.
licenseBlock
Indicates that an entity is prohibited or restricted from using a license or licensed resource.
-
E.
licenseProduction
Indicates that one party is authorized to manufacture or produce something under a license granted by another party.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4070c808190b633acf2a95b4e56 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.