Triple
T29981244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dream On |
E761596
|
entity |
| Predicate | intendedBroadcastStandard |
P15170
|
FINISHED |
| Object | cable television |
—
|
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: cable television | Statement: [Dream On, intendedBroadcastStandard, cable television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBroadcastStandard Context triple: [Dream On, intendedBroadcastStandard, cable television]
-
A.
intendedBroadcastBlock
Indicates that a particular content item is planned or scheduled to be aired within a specific broadcast time block.
-
B.
intendedForBroadcast
Indicates that something is meant or designated to be transmitted to an audience via a broadcast medium.
-
C.
broadcastStandard
chosen
Indicates that one entity uses, supports, or is associated with a particular broadcast transmission standard (such as a TV or radio broadcasting format).
-
D.
originallyBroadcastIn
Indicates that a broadcast (such as a TV or radio program) was first aired in a particular country, region, or market.
-
E.
typicalBroadcastFormat
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 29, 2026, 6:35 p.m.