Triple
T11387196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Wild Hare |
E269740
|
entity |
| Predicate | catchphraseOrigin |
P74838
|
FINISHED |
| Object | Bugs Bunny’s line "What’s up, Doc?" |
—
|
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: Bugs Bunny’s line "What’s up, Doc?" | Statement: [A Wild Hare, catchphraseOrigin, Bugs Bunny’s line "What’s up, Doc?"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catchphraseOrigin Context triple: [A Wild Hare, catchphraseOrigin, Bugs Bunny’s line "What’s up, Doc?"]
-
A.
sloganOrigin
Indicates the source or origin from which a particular slogan was created, derived, or adopted.
-
B.
featuresCatchphrase
Indicates that an entity prominently includes or is associated with a particular catchphrase.
-
C.
mottoDerivedFrom
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
-
D.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
E.
characterCatchphrase
chosen
Indicates that a particular phrase is commonly and distinctively used by a character as their 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e70b228c8190b87f5101fd683788 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.