Triple
T16572606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bluth |
E402623
|
entity |
| Predicate | hasRunningGagInvolving |
P94189
|
FINISHED |
| Object | stair car |
—
|
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: stair car | Statement: [Bluth, hasRunningGagInvolving, stair car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRunningGagInvolving Context triple: [Bluth, hasRunningGagInvolving, stair car]
-
A.
notableGag
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
B.
hasRecurringGag
chosen
Indicates that a particular joke, situation, or comedic element repeatedly appears in relation to an entity (such as a character, series, or work).
-
C.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
D.
hasComedyShows
Indicates that one entity offers, features, or includes comedy shows associated with another entity.
-
E.
isHumorousCharacter
Indicates that the character is portrayed in a humorous way or primarily serves a comedic role in the context.
- 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_69e35959f1748190934b263d6bc94143 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.