Triple
T25137446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Hudnut cosmetics brand |
E629698
|
entity |
| Predicate | usedMarketingChannel |
P39891
|
FINISHED |
| Object | magazine advertising |
—
|
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: magazine advertising | Statement: [Richard Hudnut cosmetics brand, usedMarketingChannel, magazine advertising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedMarketingChannel Context triple: [Richard Hudnut cosmetics brand, usedMarketingChannel, magazine advertising]
-
A.
hasMarketingChannel
chosen
Indicates that an entity utilizes or is associated with a particular marketing channel for promotion or communication.
-
B.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
C.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
D.
usedInMarketingMaterials
Indicates that something is included or featured as part of marketing or promotional materials.
-
E.
marketingUse
Indicates that something is used for marketing purposes, such as promotion, advertising, or brand communication.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:29 a.m.