Triple
T35238038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Company Limited |
E1017428
|
entity |
| Predicate | hasDiscountGroceryBanner |
P9238
|
FINISHED |
| Object | FreshCo |
—
|
NE NERFINISHED |
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: FreshCo | Statement: [Empire Company Limited, hasDiscountGroceryBanner, FreshCo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscountGroceryBanner Context triple: [Empire Company Limited, hasDiscountGroceryBanner, FreshCo]
-
A.
supportsDiscounts
Indicates that an entity provides or is compatible with special price reductions or promotional discounts.
-
B.
hasCouponRate
Indicates the interest rate or periodic interest payment percentage associated with a bond or similar fixed-income instrument.
-
C.
hasPromotionMethod
Indicates the method or strategy by which something is promoted or advertised.
-
D.
offersDiscountsOn
chosen
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
E.
supportsInStorePromotions
Indicates that an entity enables or accommodates promotional activities conducted within a physical store environment.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:02 p.m.