Triple
T29559438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devolver Digital |
E749997
|
entity |
| Predicate | styleOfMarketing |
P48415
|
FINISHED |
| Object | self-parody |
—
|
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: self-parody | Statement: [Devolver Digital, styleOfMarketing, self-parody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfMarketing Context triple: [Devolver Digital, styleOfMarketing, self-parody]
-
A.
brandingStyle
Indicates the specific visual and stylistic approach used to represent a brand’s identity.
-
B.
marketingTone
Indicates that one entity communicates with another using language or style intended to promote, persuade, or influence perception, typically for marketing or advertising purposes.
-
C.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
D.
typicalMarketingEmphasis
Indicates that an entity’s marketing efforts characteristically focus on or prioritize a particular theme, feature, or message.
-
E.
hasMarketingTheme
chosen
Indicates that an entity is associated with or characterized by a particular marketing theme or campaign concept.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 5:18 p.m.