Triple
T19770296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twin Cities Premium Outlets |
E474865
|
entity |
| Predicate | discountModel |
P100188
|
FINISHED |
| Object | outlet pricing |
—
|
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: outlet pricing | Statement: [Twin Cities Premium Outlets, discountModel, outlet pricing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discountModel Context triple: [Twin Cities Premium Outlets, discountModel, outlet pricing]
-
A.
discountRate
Indicates the percentage or amount by which a price, cost, or value is reduced relative to its original level.
-
B.
discountMechanism
chosen
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.
couponFloor
Indicates the minimum coupon rate or value applicable in a financial or discount arrangement, below which the coupon cannot fall.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6535ab298819085263dc37cc898cb |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.