Triple
T35011959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crown Store |
E1009956
|
entity |
| Predicate | discountsFor |
P9238
|
FINISHED |
| Object | ESO Plus subscribers |
—
|
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: ESO Plus subscribers | Statement: [Crown Store, discountsFor, ESO Plus subscribers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discountsFor Context triple: [Crown Store, discountsFor, ESO Plus subscribers]
-
A.
offersDiscountsOn
chosen
Indicates that one entity provides price reductions or special discount deals specifically applied to another entity or its associated items or services.
-
B.
discountRate
Indicates the percentage or amount by which a price, cost, or value is reduced relative to its original level.
-
C.
supportsDiscounts
Indicates that an entity provides or is compatible with special price reductions or promotional discounts.
-
D.
discountMechanism
Indicates a relationship where one entity defines the method, rule, or process by which a discount is calculated, applied, or granted to another entity.
-
E.
bargainsFor
Indicates that one entity negotiates or seeks to obtain another entity, typically aiming for more favorable terms or conditions.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.