Triple
T2522852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ipanema Gisele Bündchen sandals |
E55562
|
entity |
| Predicate | priceSegment |
P18022
|
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: [Ipanema Gisele Bündchen sandals, priceSegment, affordable fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceSegment Context triple: [Ipanema Gisele Bündchen sandals, priceSegment, affordable fashion]
-
A.
priceCategory
chosen
Indicates the classification of an item or service based on its price level or cost range.
-
B.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
C.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
D.
pricingCharacteristic
Indicates how the price of something is determined, structured, or behaves (e.g., fixed, variable, discounted, tiered).
-
E.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.