Triple
T18800356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 Glacier Deep Archive |
E459740
|
entity |
| Predicate | pricingComponent |
P60457
|
FINISHED |
| Object | storage per GB-month |
—
|
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: storage per GB-month | Statement: [S3 Glacier Deep Archive, pricingComponent, storage per GB-month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pricingComponent Context triple: [S3 Glacier Deep Archive, pricingComponent, storage per GB-month]
-
A.
productPricing
chosen
Indicates the pricing details or cost structure assigned to a specific product.
-
B.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
C.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
D.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02332d88190b68feea7f2f86d06 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.