Triple
T24452665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack of All Trades |
E616588
|
entity |
| Predicate | firstRunSyndicationBlock |
P152855
|
FINISHED |
| Object | Back2Back Action Hour |
—
|
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: Back2Back Action Hour | Statement: [Jack of All Trades, firstRunSyndicationBlock, Back2Back Action Hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunSyndicationBlock Context triple: [Jack of All Trades, firstRunSyndicationBlock, Back2Back Action Hour]
-
A.
firstBlockMessage
Indicates that this is the initial message sent in the context of a blocking action or block-related interaction between entities.
-
B.
firstBroadcast
Indicates the date or event of the initial public transmission or airing of a program, signal, or content.
-
C.
firstRunViewership
Indicates the number of viewers who watched a program during its initial (first) broadcast or release.
-
D.
firstInstallation
Indicates that an entity represents the earliest or initial installation event or instance associated with another entity.
-
E.
firstRunMedium
chosen
Indicates that an entity’s initial or earliest run, showing or execution occurred in a specified medium or channel.
- 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29859b824819087d4c7550dcbc426 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.