Triple
T4830325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "M’m! M’m! Good!" |
E107928
|
entity |
| Predicate | productCategoryPromoted |
P36108
|
FINISHED |
| Object | soup |
—
|
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: soup | Statement: ["M’m! M’m! Good!", productCategoryPromoted, soup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productCategoryPromoted Context triple: ["M’m! M’m! Good!", productCategoryPromoted, soup]
-
A.
productTypePromoted
chosen
Indicates that a particular type or category of product is being actively promoted or highlighted, such as through marketing, placement, or special offers.
-
B.
offersProductCategory
Indicates that a provider or seller makes products belonging to a specific product category available.
-
C.
promotionType
Indicates the specific kind or category of promotion associated with an entity or event.
-
D.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
E.
promotionalCampaign
Indicates a relationship where one entity organizes or runs a coordinated set of marketing activities aimed at promoting another entity, product, or service.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.