Triple
T21761464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nike Factory Store |
E537173
|
entity |
| Predicate | typicalDiscount |
P129461
|
FINISHED |
| Object | below full-price Nike retail |
—
|
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: below full-price Nike retail | Statement: [Nike Factory Store, typicalDiscount, below full-price Nike retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDiscount Context triple: [Nike Factory Store, typicalDiscount, below full-price Nike retail]
-
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.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
D.
supportsDiscounts
Indicates that an entity provides or is compatible with special price reductions or promotional discounts.
-
E.
typicalRate
chosen
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d9369f88190b4be11b82fe75a17 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:50 p.m.