Triple
T37227463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Dastardly |
E923041
|
entity |
| Predicate | hasPetPhrase |
P192137
|
FINISHED |
| Object | Muttley, do something! |
—
|
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: Muttley, do something! | Statement: [Dick Dastardly, hasPetPhrase, Muttley, do something!]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPetPhrase Context triple: [Dick Dastardly, hasPetPhrase, Muttley, do something!]
-
A.
hasCatchphraseText
chosen
Indicates that an entity is associated with a specific catchphrase expressed as text.
-
B.
hasCatchphraseElement
Indicates that one entity is a component, word, or segment that forms part of another entity’s catchphrase.
-
C.
hasCatchphraseStatus
Indicates whether an entity’s phrase or expression holds the status of being recognized as a catchphrase.
-
D.
hasNotablePhrase
Indicates that an entity is associated with a specific phrase or expression that is considered notable or characteristic of it.
-
E.
usedPhrase
Indicates that one entity employed or expressed a particular phrase in speech, writing, or another form of communication.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 3, 2026, 4:15 p.m.