Triple
T35238022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Company Limited |
E1017428
|
entity |
| Predicate | notableBrandPortfolioIncludes |
P181690
|
FINISHED |
| Object | Sobeys |
E329231
|
NE 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: Sobeys | Statement: [Empire Company Limited, notableBrandPortfolioIncludes, Sobeys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBrandPortfolioIncludes Context triple: [Empire Company Limited, notableBrandPortfolioIncludes, Sobeys]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
C.
hasBrandPortfolioRange
chosen
Indicates that an entity maintains or offers a specific range or collection of brands within its overall brand portfolio.
-
D.
partOfBrandPortfolioOf
Indicates that one brand is included within, and belongs to, the overall brand portfolio of another entity.
-
E.
brandsAs
Indicates that one entity assigns a particular brand identity or label to another entity.
- F. None of above.
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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3823b422a081909d20aa448613d8ff |
completed | June 21, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.