Triple
T23467242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leave It to Beaver |
E569127
|
entity |
| Predicate | originalChannelOrder |
P2595
|
FINISHED |
| Object | first on CBS |
—
|
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: first on CBS | Statement: [Leave It to Beaver, originalChannelOrder, first on CBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalChannelOrder Context triple: [Leave It to Beaver, originalChannelOrder, first on CBS]
-
A.
channelOrder
Indicates the sequence or priority assigned to channels relative to one another.
-
B.
originalChannel
chosen
Indicates the communication channel or medium through which something was first created, sent, or published.
-
C.
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.
-
D.
originalOrder
Indicates that the entities are arranged or referenced according to their initial, unaltered sequence or configuration.
-
E.
originalChannelGroup
Indicates that one entity is the initial or primary channel group from which another channel or grouping is derived or associated.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6fc35c48190a67614fb4170f15b |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.