Triple
T25247457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anna Molly |
E632641
|
entity |
| Predicate | hasWordplayBasedTitle |
P36401
|
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: [Anna Molly, hasWordplayBasedTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWordplayBasedTitle Context triple: [Anna Molly, hasWordplayBasedTitle, true]
-
A.
hasTitlePun
chosen
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
B.
taglineWordplay
Indicates that a tagline employs wordplay, such as puns, double meanings, or playful language, as a key part of its expression.
-
C.
hasEnigmaticTitle
Indicates that an entity possesses a title or designation that is mysterious, obscure, or difficult to interpret.
-
D.
titleAlludesTo
Indicates that one title makes an indirect or suggestive reference to the content, theme, or another work associated with the other.
-
E.
isPlayOnWordsWith
Indicates a relationship where one expression is a pun or wordplay that depends on, echoes, or cleverly twists the wording or meaning of another 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 21, 2026, 1:10 p.m.