Triple
T3303743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thursday Night Football |
E69396
|
entity |
| Predicate | rightsHolderFromYear |
P47914
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Thursday Night Football, rightsHolderFromYear, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightsHolderFromYear Context triple: [Thursday Night Football, rightsHolderFromYear, 2018]
-
A.
historicalRightsHolder
Indicates that an entity previously held rights or ownership over something during a past period, but no longer does so in the present.
-
B.
rightsHolderRecognition
Indicates that an entity formally acknowledges or identifies another entity as the legitimate holder of specific rights.
-
C.
hasCopyrightHolder
Indicates that a specified entity holds the legal copyright ownership or rights over another entity.
-
D.
namingRightsHolder
Indicates which entity holds the official right to name or brand another entity (such as a venue, event, or asset).
-
E.
rightHolder
Indicates that one entity holds or possesses a legal or contractual right in relation to another entity or resource.
- F. None of above. chosen
Provenance (4 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0c662308190aad8b2a93e1c8a5c |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada42625308190be257f16a623a410 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.