Triple
T36364985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Hero Sits Next Door |
E895595
|
entity |
| Predicate | hasOpeningGag |
P52455
|
FINISHED |
| Object | cutaway gags typical of Family Guy |
—
|
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: cutaway gags typical of Family Guy | Statement: [A Hero Sits Next Door, hasOpeningGag, cutaway gags typical of Family Guy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningGag Context triple: [A Hero Sits Next Door, hasOpeningGag, cutaway gags typical of Family Guy]
-
A.
notableGag
chosen
Indicates that something features a particularly memorable or significant joke, comedic moment, or running gag.
-
B.
hasOpeningScene
Indicates that a work (such as a film, show, or story) possesses a specific initial scene that begins or introduces its narrative.
-
C.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
D.
hasComedyElements
Indicates that something contains humorous or comedic aspects as part of its overall content or style.
-
E.
openedComedyClub
Indicates that an entity initiated and established a comedy club, making it operational for performances or business.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:10 p.m.