Triple
T32081579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnatune |
E819310
|
entity |
| Predicate | licensingTarget |
P15136
|
FINISHED |
| Object | film producers |
—
|
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: film producers | Statement: [Magnatune, licensingTarget, film producers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensingTarget Context triple: [Magnatune, licensingTarget, film producers]
-
A.
licensorOf
Indicates that one entity grants another entity permission or rights to use, produce, or distribute something under specified terms.
-
B.
licensingComponent
Indicates that one entity serves as a licensing-related component or module within the context or operation of another entity.
-
C.
licensingChannel
Indicates the medium or route through which a license is obtained, distributed, or managed between parties.
-
D.
licensingRestriction
Indicates that there is a constraint or condition imposed on the use, distribution, or modification of something under a specific license.
-
E.
licensee
chosen
Indicates that one entity is authorized by another, through a license agreement, to use or exploit certain rights, property, or resources.
- 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:24 a.m.