Triple
T37710440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | You Bet Your Life |
E939315
|
entity |
| Predicate | finalRadioAirDate |
P199516
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [You Bet Your Life, finalRadioAirDate, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalRadioAirDate Context triple: [You Bet Your Life, finalRadioAirDate, 1956]
-
A.
specialEpisodeAirDate
Indicates the calendar date on which a special episode is broadcast or made available to the public.
-
B.
radioReleaseDate
Indicates the date on which something (typically a song, program, or broadcast content) was first released or made available on radio.
-
C.
airdateDetail
Indicates the specific broadcast scheduling information for something, such as its original air date, time, or related airing details.
-
D.
firstBroadcastEndDate
Indicates the date on which the initial broadcast of something (such as a program or event) concluded.
-
E.
firstRadioBroadcastDate
Indicates the date on which an entity’s first radio broadcast took place.
- F. None of above. chosen
Provenance (4 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
| PDg | Predicate description generation | batch_69ff3fb151008190bf8a90f9f1c5f0c8 |
completed | May 9, 2026, 2:07 p.m. |
Created at: May 3, 2026, 4:18 p.m.