Triple
T12321992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS Lambda |
E293752
|
entity |
| Predicate | billedIncrements |
P79845
|
FINISHED |
| Object | 1 millisecond (for new pricing model) |
—
|
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: 1 millisecond (for new pricing model) | Statement: [AWS Lambda, billedIncrements, 1 millisecond (for new pricing model)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billedIncrements Context triple: [AWS Lambda, billedIncrements, 1 millisecond (for new pricing model)]
-
A.
billingGranularity
chosen
Indicates the level of detail or unit (such as per item, per hour, or per month) at which charges are calculated and presented in billing.
-
B.
billingMetric
Indicates a relationship where a specific metric or measure is used as the basis for calculating billing or charges between entities.
-
C.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
D.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
E.
billedFrom
Indicates that a bill, invoice, or charge originates from or is issued by a particular source or entity.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:53 p.m.