Triple
T17499762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AWS Auto Scaling |
E426158
|
entity |
| Predicate | supportsMetricType |
P24486
|
FINISHED |
| Object | CPU utilization |
—
|
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: CPU utilization | Statement: [AWS Auto Scaling, supportsMetricType, CPU utilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMetricType Context triple: [AWS Auto Scaling, supportsMetricType, CPU utilization]
-
A.
hasMetricType
Indicates that something is associated with or characterized by a specific type or category of metric.
-
B.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
D.
supportsTestType
Indicates that one entity is capable of handling, executing, or being compatible with a specified type of test.
-
E.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452112ff0819089c2951baba90102 |
completed | April 19, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.