Triple
T34885908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denner |
E1006142
|
entity |
| Predicate | hasPrivateLabelProducts |
P191670
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Denner, hasPrivateLabelProducts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrivateLabelProducts Context triple: [Denner, hasPrivateLabelProducts, yes]
-
A.
hasPrivateLabelBrands
chosen
Indicates that an entity offers or is associated with products sold under its own exclusive private-label brands rather than only third-party brands.
-
B.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
-
C.
hasNumberOfBrands
Indicates the relationship where an entity is associated with a specific count of brands it possesses or encompasses.
-
D.
hasRetailBrands
Indicates that an entity owns, manages, or is associated with one or more retail brands.
-
E.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a033029023481909d9fa4a76b954879 |
completed | May 12, 2026, 1:50 p.m. |
| PD | Predicate disambiguation | batch_6a032d9f1fa48190bd1c94a8f930d02c |
completed | May 12, 2026, 1:39 p.m. |
Created at: May 3, 2026, 4 p.m.