Triple
T19999802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Who's Afraid of the Big Bad Wolf?" |
E494286
|
entity |
| Predicate | hasCatchphraseStatus |
P138293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: ["Who's Afraid of the Big Bad Wolf?", hasCatchphraseStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchphraseStatus Context triple: ["Who's Afraid of the Big Bad Wolf?", hasCatchphraseStatus, true]
-
A.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
-
B.
notableCatchphraseUser
Indicates that the subject is a person who is notably associated with using a particular catchphrase.
-
C.
characterCatchphrase
Indicates that a particular phrase is commonly and distinctively used by a character as their catchphrase.
-
D.
featuresCatchphrase
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
E.
hasNotablePhrase
Indicates that an entity is associated with a specific phrase or expression that is considered notable or characteristic of it.
- F. None of above. chosen
Provenance (4 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a15f308190a99ac3205f948acb |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:32 p.m.