Triple
T21463400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up the Junction |
E529529
|
entity |
| Predicate | broadcastSlot |
P14564
|
FINISHED |
| Object | Wednesday evening |
—
|
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: Wednesday evening | Statement: [Up the Junction, broadcastSlot, Wednesday evening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastSlot Context triple: [Up the Junction, broadcastSlot, Wednesday evening]
-
A.
broadcastTimeSlot
chosen
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
B.
broadcastBlock
Indicates that one entity transmits or disseminates a block (such as a data block or message) to multiple recipients or across a network.
-
C.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
-
D.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
E.
broadcastBand
Indicates that something is transmitted over a particular broadcast frequency band (e.g., AM, FM, VHF, UHF) for distribution to receivers.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9efdb188190be79b72e1bd18860 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.