Triple
T8503019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn & Teller |
E201267
|
entity |
| Predicate | hasRegularShow |
P82865
|
FINISHED |
| Object | Penn & Teller at the Rio |
—
|
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: Penn & Teller at the Rio | Statement: [Penn & Teller, hasRegularShow, Penn & Teller at the Rio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularShow Context triple: [Penn & Teller, hasRegularShow, Penn & Teller at the Rio]
-
A.
hasFictionalShowWithinShow
Indicates that one show contains or features another fictional show within its narrative.
-
B.
hasMainStudioShow
Indicates that an entity serves as the primary studio-based show associated with another entity (such as a network, channel, or program brand).
-
C.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
D.
hasPublicProgram
Indicates that an entity offers or participates in a program or initiative that is accessible to the general public.
-
E.
hasRadioShow
Indicates that an entity hosts, produces, or is responsible for a radio show.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59c413881909513d8a9d52333c0 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:14 p.m.