Triple
T3303737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thursday Night Football |
E69396
|
entity |
| Predicate | simulcastPartnerFromYear |
P47912
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Thursday Night Football, simulcastPartnerFromYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: simulcastPartnerFromYear Context triple: [Thursday Night Football, simulcastPartnerFromYear, 2014]
-
A.
simulcastsOn
Indicates that a broadcast (such as a TV or radio program) is transmitted simultaneously on the specified channel, platform, or service.
-
B.
performingPartner
Indicates that one entity is the partner who participates in or carries out a performance together with another entity.
-
C.
isMultiSeasonParticipantOf
Indicates that an entity has participated in the related entity across multiple seasons or iterations.
-
D.
joinedConferenceYear
Indicates the year in which an entity became a participant or member of a particular conference.
-
E.
hasOnscreenPartner
Indicates that one entity appears together with another as a partner within the same onscreen context or scene.
- 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.