Triple
T18800412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S3 Object Lambda |
E459741
|
entity |
| Predicate | billedFor |
P91060
|
FINISHED |
| Object | Lambda compute duration |
—
|
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: Lambda compute duration | Statement: [S3 Object Lambda, billedFor, Lambda compute duration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billedFor Context triple: [S3 Object Lambda, billedFor, Lambda compute duration]
-
A.
billedFrom
Indicates that a bill, invoice, or charge originates from or is issued by a particular source or entity.
-
B.
billedBy
chosen
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
C.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
D.
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.
-
E.
budgetChargedOn
Indicates that a specific budget is debited or applied as the source of funds for a given cost, transaction, or activity.
- 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.