Triple
T19434053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Block Volume |
E486186
|
entity |
| Predicate | hasBillingModel |
P97754
|
FINISHED |
| Object | pay-as-you-go |
—
|
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: pay-as-you-go | Statement: [Oracle Block Volume, hasBillingModel, pay-as-you-go]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBillingModel Context triple: [Oracle Block Volume, hasBillingModel, pay-as-you-go]
-
A.
usesBillingModel
chosen
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
B.
hasPaymentModel
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
C.
hasBasePlan
Indicates that an entity is associated with or derived from a specified foundational or default plan.
-
D.
usesRevenueModel
Indicates that one entity applies or operates according to a particular revenue model to generate income.
-
E.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6335dae10819096e1825741f814ed |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.