Triple
T29020363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duff Lite |
E737434
|
entity |
| Predicate | labelDesignFamily |
P96100
|
FINISHED |
| Object | Duff brand packaging |
—
|
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: Duff brand packaging | Statement: [Duff Lite, labelDesignFamily, Duff brand packaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelDesignFamily Context triple: [Duff Lite, labelDesignFamily, Duff brand packaging]
-
A.
serviceDesignationFamily
Indicates that one service designation is part of the same family or grouping as another, reflecting a shared classification or closely related category.
-
B.
designedByFamilyOf
Indicates that something was created, planned, or conceived by one or more members of a particular family or familial group.
-
C.
brandingFamily
chosen
Indicates that one entity belongs to, or is associated with, a particular brand family or group under a shared branding strategy.
-
D.
lineFamily
Indicates that two entities belong to the same family or lineage associated with a particular line (e.g., a family line or line-based grouping).
-
E.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 9:48 a.m.