Triple
T27730680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EA Play for PC |
E697421
|
entity |
| Predicate | discountScope |
P44269
|
FINISHED |
| Object | applies to full games |
—
|
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: applies to full games | Statement: [EA Play for PC, discountScope, applies to full games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discountScope Context triple: [EA Play for PC, discountScope, applies to full games]
-
A.
discountRate
Indicates the percentage or amount by which a price, cost, or value is reduced relative to its original level.
-
B.
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.
-
C.
promotionScope
chosen
Indicates the range or extent within which a promotion or promotional offer is valid or applicable.
-
D.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
E.
usesDiscountFactor
Indicates that an entity applies a discount factor when evaluating or calculating the value of something over time or across scenarios.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 3:11 p.m.