Triple
T34231460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Olson |
E878205
|
entity |
| Predicate | knownForCatchphrase |
P126963
|
FINISHED |
| Object | “Come on down!” |
—
|
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: “Come on down!” | Statement: [Johnny Olson, knownForCatchphrase, “Come on down!”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCatchphrase Context triple: [Johnny Olson, knownForCatchphrase, “Come on down!”]
-
A.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
-
B.
notableCatchphraseUser
chosen
Indicates that the subject is a person who is notably associated with using a particular catchphrase.
-
C.
becameCatchphraseIn
Indicates that a phrase or expression came to be widely recognized and used as a catchphrase within a particular context, group, or time period.
-
D.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
-
E.
hasCatchphraseStatus
Indicates whether an entity’s phrase or expression holds the status of being recognized as a catchphrase.
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:56 a.m.