Triple
T29356049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Odd Couple: The Special |
E744445
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | television reunion special |
C13509
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: television reunion special Context triple: [The Odd Couple: The Special, instanceOf, television reunion special]
-
A.
reunion special
chosen
A reunion special is a television or streaming program that brings together the cast or participants of a previous show or season to reflect on events, share updates, and often reveal behind-the-scenes insights.
-
B.
recurring television special
A recurring television special is a periodically broadcast program, often tied to a specific theme, event, or season, that returns at regular intervals outside the standard episodic series format.
-
C.
television event
A television event is a scheduled broadcast program or special presentation designed for viewing on television, often characterized by its significance, live nature, or anticipated large audience.
-
D.
television special song
A television special song is a musical piece composed or selected specifically to feature prominently in a one-time or limited-run TV program, often enhancing its theme, narrative, or promotional appeal.
-
E.
American television special
An American television special is a standalone, typically one-time or limited-run broadcast program produced for U.S. television that falls outside the regular episodic series format, often created for holidays, events, or unique occasions.
- F. None of above.
Provenance (1 batch)
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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:12 p.m.