Triple
T18800273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 Glacier Instant Retrieval |
E459739
|
entity |
| Predicate | retrievalTime |
P133065
|
FINISHED |
| Object | milliseconds |
—
|
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: milliseconds | Statement: [S3 Glacier Instant Retrieval, retrievalTime, milliseconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retrievalTime Context triple: [S3 Glacier Instant Retrieval, retrievalTime, milliseconds]
-
A.
retrievalDate
Indicates the date on which an item, record, or resource was accessed, obtained, or retrieved.
-
B.
timeOfReturn
Indicates the specific time at which an entity comes back to a prior location or state.
-
C.
recoveryDate
Indicates the date on which a recovery process or restoration of a prior state is completed or officially recorded.
-
D.
timeIndexed
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
-
E.
latestTime
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.