Triple

T18800540
Position Surface form Disambiguated ID Type / Status
Subject S3 One Zone-IA E459744 entity
Predicate minimumBillableObjectSize P112219 FINISHED
Object 128 KB for storage charges 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: 128 KB for storage charges | Statement: [S3 One Zone-IA, minimumBillableObjectSize, 128 KB for storage charges]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: minimumBillableObjectSize
Context triple: [S3 One Zone-IA, minimumBillableObjectSize, 128 KB for storage charges]
  • A. minimumUnitSize
    Indicates that there is a smallest allowable or defined size or quantity for the unit involved in the relationship.
  • B. minimumSize chosen
    Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
  • C. minimumFrameSize
    Indicates the smallest allowable or supported size of a frame in the given context or system.
  • D. recommendedMinimumSize
    Indicates the smallest size that is advised or suggested as a minimum for something to be used or considered appropriate.
  • E. minimumDenomination
    Indicates that one entity specifies the smallest allowable unit or value (minimum denomination) in which another entity can be expressed, transacted, or divided.
  • 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.