Triple
T35866193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupperware Brands |
E1037093
|
entity |
| Predicate | coreChannel |
P184217
|
FINISHED |
| Object | independent sales consultants |
—
|
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: independent sales consultants | Statement: [Tupperware Brands, coreChannel, independent sales consultants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreChannel Context triple: [Tupperware Brands, coreChannel, independent sales consultants]
-
A.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
B.
targetChannel
Indicates the specific channel or medium through which an action, message, or effect is directed toward its intended recipient.
-
C.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
D.
primaryChannel
Indicates that one channel is designated as the main or most important channel among a set of available channels.
-
E.
linearChannel
Indicates a relationship where communication or flow occurs through a single, sequential path or medium, typically in one dimension or along a straight route.
- F. None of above. chosen
Provenance (4 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:06 p.m.