Triple
T28431072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Would I Lie to You? |
E715129
|
entity |
| Predicate | isBroadcastAs |
P154302
|
FINISHED |
| Object | pre-recorded show |
—
|
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: pre-recorded show | Statement: [Would I Lie to You?, isBroadcastAs, pre-recorded show]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBroadcastAs Context triple: [Would I Lie to You?, isBroadcastAs, pre-recorded show]
-
A.
wasBroadcastAs
chosen
Indicates that one entity (such as a program, event, or content item) was transmitted or aired to an audience under the form, title, or version represented by another entity.
-
B.
originallyBroadcastAs
Indicates that one media work was first transmitted or aired under a particular title or version.
-
C.
intendedForBroadcast
Indicates that something is meant or designated to be transmitted to an audience via a broadcast medium.
-
D.
hasBroadcaster
Indicates that an entity is associated with or transmitted by a particular broadcaster or broadcasting organization.
-
E.
oftenBroadcastAs
Indicates that something is frequently transmitted or aired through a broadcast medium under a particular form, title, or version.
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:39 a.m.