Triple
T35524358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tags Boutique |
E1026630
|
entity |
| Predicate | productPricePositioning |
P8244
|
FINISHED |
| Object | affordable fashion |
—
|
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: affordable fashion | Statement: [Tags Boutique, productPricePositioning, affordable fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productPricePositioning Context triple: [Tags Boutique, productPricePositioning, affordable fashion]
-
A.
productPricing
Indicates the pricing details or cost structure assigned to a specific product.
-
B.
pricingStrategy
chosen
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
C.
definesPriceFor
Indicates that one entity specifies or establishes the price applicable to another entity.
-
D.
productStrategy
Indicates the strategic relationship in which an entity defines, plans, or guides the direction, positioning, and evolution of a product or product portfolio.
-
E.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:04 p.m.