Triple
T6507325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfect Harmony |
E150042
|
entity |
| Predicate | originalNetworkTimeslot |
P14564
|
FINISHED |
| Object | Thursday 8:30 PM |
—
|
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: Thursday 8:30 PM | Statement: [Perfect Harmony, originalNetworkTimeslot, Thursday 8:30 PM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalNetworkTimeslot Context triple: [Perfect Harmony, originalNetworkTimeslot, Thursday 8:30 PM]
-
A.
broadcastTimeSlot
chosen
Indicates the specific time period during which a broadcast (such as a TV or radio program) is scheduled to air.
-
B.
originalNetworkUsage
Indicates the amount or pattern of network resources initially consumed or utilized in a given context or time period.
-
C.
originalRunStartNetwork
Indicates the network on which a program or series first began its original broadcast run.
-
D.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
-
E.
originalTimeInterval
Indicates the initial or primary time span during which an event, state, or relationship is considered to occur, before any adjustments or derived intervals.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f386aa08190bfc8592a92ec6339 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab714908190aa7c2fbf64078e15 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.