Triple
T12015637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL on Fox |
E286015
|
entity |
| Predicate | primaryRightsPackage |
P45186
|
FINISHED |
| Object | NFC regular-season games |
—
|
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: NFC regular-season games | Statement: [NFL on Fox, primaryRightsPackage, NFC regular-season games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRightsPackage Context triple: [NFL on Fox, primaryRightsPackage, NFC regular-season games]
-
A.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
B.
rightsInclude
chosen
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
C.
primaryOwner
Indicates that one entity is the main or principal owner of another entity, having the highest level of ownership or control among all possible owners.
-
D.
rightsManagement
Indicates the management, control, and enforcement of usage rights or permissions associated with an entity or resource.
-
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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.