Triple
T37657857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure Reserved Virtual Machine Instances |
E937645
|
entity |
| Predicate | supportsBillingOption |
P46101
|
FINISHED |
| Object | upfront payment |
—
|
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: upfront payment | Statement: [Azure Reserved Virtual Machine Instances, supportsBillingOption, upfront payment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBillingOption Context triple: [Azure Reserved Virtual Machine Instances, supportsBillingOption, upfront payment]
-
A.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
B.
hasStarBilling
Indicates that an entity is given top or prominently featured billing in a production or presentation.
-
C.
hasPaymentOption
chosen
Indicates that an entity supports or offers a particular method or option for making payments.
-
D.
supportsCodeRates
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
E.
supportsMonetizationProgram
Indicates that an entity enables or is compatible with a specific monetization program, allowing revenue-generating activities to occur.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.