Triple
T34237647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Froot Loops |
E878376
|
entity |
| Predicate | isMarketedWith |
P119077
|
FINISHED |
| Object | animated commercials |
—
|
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: animated commercials | Statement: [Froot Loops, isMarketedWith, animated commercials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMarketedWith Context triple: [Froot Loops, isMarketedWith, animated commercials]
-
A.
marketedWith
chosen
Indicates that two or more products or services are promoted together as part of the same marketing effort or campaign.
-
B.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
C.
alsoMarketedIn
Indicates that a product or service is additionally marketed or sold in another specified market or region.
-
D.
hasMarketingElement
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
E.
marketedFrom
Indicates that a product, service, or offering began to be marketed starting from a specified time or date.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.