Triple
T18800359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 Glacier Deep Archive |
E459740
|
entity |
| Predicate | minimumStorageDuration |
P102162
|
FINISHED |
| Object | 180 days |
—
|
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: 180 days | Statement: [S3 Glacier Deep Archive, minimumStorageDuration, 180 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumStorageDuration Context triple: [S3 Glacier Deep Archive, minimumStorageDuration, 180 days]
-
A.
dataRetentionPeriod
Indicates the length of time data is stored or kept before it is deleted, archived, or otherwise disposed of.
-
B.
minStorageCapacity
Indicates the minimum storage capacity required, allowed, or guaranteed in a given context or relationship.
-
C.
canBeStoredFor
chosen
Indicates that something is suitable or allowed to be kept in storage for a certain duration or under certain conditions.
-
D.
existencePeriod
Indicates the time span during which an entity exists or is valid.
-
E.
typicalExpirationPeriod
Indicates the usual length of time after which something is expected to expire or become invalid.
- 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.