Triple
T36125889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackout (game show) |
E1044878
|
entity |
| Predicate | airedOpposite |
P158198
|
FINISHED |
| Object | Sale of the Century |
—
|
NE NERFINISHED |
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: Sale of the Century | Statement: [Blackout (game show), airedOpposite, Sale of the Century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airedOpposite Context triple: [Blackout (game show), airedOpposite, Sale of the Century]
-
A.
airedAs
Indicates that one media work was broadcast or presented under a particular title, format, or version.
-
B.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
C.
airedTogetherWith
chosen
Indicates that two media items (such as episodes or programs) were broadcast during the same time period or as part of the same airing schedule.
-
D.
airedOn
Indicates that a broadcasted program or episode was shown on a specific channel, platform, or medium.
-
E.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.