Triple
T37938201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinky and the Brain |
E946406
|
entity |
| Predicate | intendedChannelBlock |
P99032
|
FINISHED |
| Object | Kids' WB Saturday morning |
—
|
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: Kids' WB Saturday morning | Statement: [Pinky and the Brain, intendedChannelBlock, Kids' WB Saturday morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedChannelBlock Context triple: [Pinky and the Brain, intendedChannelBlock, Kids' WB Saturday morning]
-
A.
originalChannelBlock
Indicates that one channel or source is the initial or primary origin from which another channel, block, or content segment is derived or constructed.
-
B.
laterChannelBlock
Indicates that one communication channel block occurs chronologically after another channel block.
-
C.
intendedBroadcastBlock
chosen
Indicates that a particular content item is planned or scheduled to be aired within a specific broadcast time block.
-
D.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
E.
basedOnChannel
Indicates that something is determined, derived, or decided according to a particular channel as its basis or reference.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:20 p.m.