Triple
T37657855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure Reserved Virtual Machine Instances |
E937645
|
entity |
| Predicate | supportsTermLength |
P204309
|
FINISHED |
| Object | 1-year term |
—
|
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-year term | Statement: [Azure Reserved Virtual Machine Instances, supportsTermLength, 1-year term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTermLength Context triple: [Azure Reserved Virtual Machine Instances, supportsTermLength, 1-year term]
-
A.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
B.
supportsKeyLength
Indicates that one entity is capable of handling, accepting, or operating with a specified cryptographic key length associated with another entity.
-
C.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
D.
hasCommonTermLength
Indicates that two or more entities share the same duration or length for a specified term or period.
-
E.
maximumTermCount
Indicates the highest number of terms that are allowed or considered within a given context or operation.
- F. None of above. chosen
Provenance (4 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.