Triple
T25524590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thums Up |
E639741
|
entity |
| Predicate | isAdvertisedThrough |
P33256
|
FINISHED |
| Object | digital media |
—
|
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: digital media | Statement: [Thums Up, isAdvertisedThrough, digital media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdvertisedThrough Context triple: [Thums Up, isAdvertisedThrough, digital media]
-
A.
advertisedUsing
chosen
Indicates that something is promoted or made known through a particular medium, method, or channel of advertising.
-
B.
advertisedAs
Indicates that something is promoted or presented to others as having a particular quality, identity, or role.
-
C.
advertises
Indicates that one entity promotes, publicizes, or markets another entity, typically to attract attention or customers.
-
D.
isDistributedThrough
Indicates that something is supplied, circulated, or made available to others via a particular channel, medium, or distribution mechanism.
-
E.
announcedThrough
Indicates that an announcement or communication was made via a particular medium, channel, or intermediary.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f85e975c8190bdadf34f099f3614 |
completed | May 2, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 3:09 p.m.