Triple
T16556560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live & Kicking |
E402220
|
entity |
| Predicate | intendedBroadcastDay |
P14563
|
FINISHED |
| Object | Saturday |
—
|
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: Saturday | Statement: [Live & Kicking, intendedBroadcastDay, Saturday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedBroadcastDay Context triple: [Live & Kicking, intendedBroadcastDay, Saturday]
-
A.
broadcastDay
chosen
Indicates the specific day on which a program, event, or content is broadcast or scheduled to be broadcast.
-
B.
intendedBroadcastBlock
Indicates that a particular content item is planned or scheduled to be aired within a specific broadcast time block.
-
C.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
D.
wasBroadcastOn
Indicates that a media item (such as a program, episode, or event) was transmitted or aired via a particular broadcast channel, station, or network.
-
E.
startsOnDay
Indicates that an event or process begins on a specified calendar day.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc99f648190b40869ce52d351c8 |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.