Triple
T25235479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen Studios |
E632324
|
entity |
| Predicate | hasMediaRightsBusiness |
P6247
|
FINISHED |
| Object | satellite rights |
—
|
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: satellite rights | Statement: [Pen Studios, hasMediaRightsBusiness, satellite rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaRightsBusiness Context triple: [Pen Studios, hasMediaRightsBusiness, satellite rights]
-
A.
mediaRightsValue
Indicates the monetary worth or valuation assigned to the rights to use, distribute, or exploit a piece of media.
-
B.
mediaRights
chosen
Indicates that one entity holds legal permission or authority to use, distribute, or control the use of another entity’s media content.
-
C.
hasBroadcastRightsHolder
Indicates that one entity holds the legal rights to broadcast content owned or controlled by another entity.
-
D.
commercialRightsHolderOf
Indicates that one entity holds the legal commercial rights to exploit, license, or profit from another entity.
-
E.
hasDistributionRights
Indicates that one entity is legally authorized to distribute another entity’s product, content, or service within specified terms or territories.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 1:07 p.m.