Triple
T12597848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mutual Sports Network |
E300777
|
entity |
| Predicate | broadcastRightsType |
P6348
|
FINISHED |
| Object | live event 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: live event rights | Statement: [Mutual Sports Network, broadcastRightsType, live event rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastRightsType Context triple: [Mutual Sports Network, broadcastRightsType, live event rights]
-
A.
mediaRightsValue
Indicates the monetary worth or valuation assigned to the rights to use, distribute, or exploit a piece of media.
-
B.
mediaRights
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.
broadcastRightsFeeUS
Indicates the amount of money paid in the United States for the rights to broadcast an event or content.
-
E.
broadcastType
chosen
Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.