Triple
T653975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fox Sports |
E11604
|
entity |
| Predicate | ownerOfRights |
P7802
|
FINISHED |
| Object | regional sports rights (various teams and conferences) |
—
|
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: regional sports rights (various teams and conferences) | Statement: [Fox Sports, ownerOfRights, regional sports rights (various teams and conferences)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerOfRights Context triple: [Fox Sports, ownerOfRights, regional sports rights (various teams and conferences)]
-
A.
rightHolder
chosen
Indicates that one entity holds or possesses a legal or contractual right in relation to another entity or resource.
-
B.
rights
Indicates that an entity possesses entitlements, permissions, or legal/moral claims in relation to another entity or context.
-
C.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
D.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
typeOfRight
Indicates the specific category or nature of a right that is held, exercised, or assigned 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f4bb5b881908a18b5ec1c94e0cf |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.