Triple
T28672137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chew Chew |
E725752
|
entity |
| Predicate | brandTypeAssociatedWith |
P108712
|
FINISHED |
| Object | dental health brand |
—
|
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: dental health brand | Statement: [Chew Chew, brandTypeAssociatedWith, dental health brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandTypeAssociatedWith Context triple: [Chew Chew, brandTypeAssociatedWith, dental health brand]
-
A.
brandAssociationType
chosen
Indicates the specific nature of the relationship or association that exists between a brand and another entity (such as a product, organization, or campaign).
-
B.
associatedBrandCategory
Indicates that a brand is linked to or classified under a particular product or service category.
-
C.
componentTypeAssociatedWithBrand
Indicates that a specific component type is linked or affiliated with a particular brand.
-
D.
brandNameType
Indicates the specific type or category associated with a brand name within a broader branding or naming system.
-
E.
brandsAs
Indicates that one entity assigns a particular brand identity or label to another entity.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 5:04 a.m.