Triple
T38117674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Quick Draw McGraw Show |
E951833
|
entity |
| Predicate | hasCatchphraseUser |
P126963
|
FINISHED |
| Object | Quick Draw McGraw |
—
|
NE NERFINISHED |
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: Quick Draw McGraw | Statement: [The Quick Draw McGraw Show, hasCatchphraseUser, Quick Draw McGraw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCatchphraseUser Context triple: [The Quick Draw McGraw Show, hasCatchphraseUser, Quick Draw McGraw]
-
A.
hasCatchphraseText
Indicates that an entity is associated with a specific catchphrase expressed as text.
-
B.
hasCatchphraseStatus
Indicates whether an entity’s phrase or expression holds the status of being recognized as a catchphrase.
-
C.
hasCatchphraseElement
Indicates that one entity is a component, word, or segment that forms part of another entity’s catchphrase.
-
D.
notableCatchphraseUser
chosen
Indicates that the subject is a person who is notably associated with using a particular catchphrase.
-
E.
hasCatchphraseStyle
Indicates that an entity’s catchphrase conforms to, or is characterized by, a particular stylistic pattern or manner of expression.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: May 3, 2026, 4:21 p.m.