Triple
T28383315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beadle's Hotshots |
E718944
|
entity |
| Predicate | typicalEpisodeContains |
P51458
|
FINISHED |
| Object | multiple prank segments |
—
|
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: multiple prank segments | Statement: [Beadle's Hotshots, typicalEpisodeContains, multiple prank segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEpisodeContains Context triple: [Beadle's Hotshots, typicalEpisodeContains, multiple prank segments]
-
A.
typicalEpisodeContent
chosen
Indicates that the specified content is characteristic or commonly found within episodes of the given series or program.
-
B.
presentInEveryEpisode
Indicates that the subject appears in all episodes of the referenced series or season.
-
C.
narrativeEpisode
Indicates that one event, scene, or segment functions as a distinct episode within a larger narrative or storyline.
-
D.
appearsInEpisodeType
Indicates that an entity is featured in, or associated with, a specific type or category of episode.
-
E.
narratesEpisode
Indicates that one entity tells or recounts a specific episode or event involving another entity.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: April 28, 2026, 1:08 a.m.