Triple
T19168336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharktopus vs. Whalewolf |
E469244
|
entity |
| Predicate | hasMarketingHook |
P85034
|
FINISHED |
| Object | versus-style monster battle |
—
|
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: versus-style monster battle | Statement: [Sharktopus vs. Whalewolf, hasMarketingHook, versus-style monster battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketingHook Context triple: [Sharktopus vs. Whalewolf, hasMarketingHook, versus-style monster battle]
-
A.
hasMarketingElement
chosen
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
B.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
C.
hasMarketingClaim
Indicates that an entity asserts or is associated with a specific marketing claim about a product, service, or brand.
-
D.
hasMarketingIcon
Indicates that an entity is associated with, or represented by, a specific marketing-related icon or symbol.
-
E.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16132e081908c6b8d576163316e |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.