Triple
T12278779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honeymooners |
E292659
|
entity |
| Predicate | famousCatchphrase |
P53722
|
FINISHED |
| Object | One of these days, Alice—pow! Right in the kisser! |
—
|
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: One of these days, Alice—pow! Right in the kisser! | Statement: [The Honeymooners, famousCatchphrase, One of these days, Alice—pow! Right in the kisser!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousCatchphrase Context triple: [The Honeymooners, famousCatchphrase, One of these days, Alice—pow! Right in the kisser!]
-
A.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
-
B.
featuresCatchphrase
chosen
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
C.
famousLineSpeaker
Indicates that the subject is the person who spoke or delivered the famous line referenced by the object.
-
D.
associatedWithFamousSlogan
Indicates that an entity is connected to, known for, or commonly linked with a particular famous slogan.
-
E.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.