Triple
T9898843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azure App Service |
E182237
|
entity |
| Predicate | hasSKU |
P54074
|
FINISHED |
| Object | Free tier |
—
|
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: Free tier | Statement: [Azure App Service, hasSKU, Free tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSKU Context triple: [Azure App Service, hasSKU, Free tier]
-
A.
hasRetailCharacteristic
Indicates that an entity possesses a specific attribute, feature, or quality relevant to retail contexts (such as pricing, packaging, or point-of-sale properties).
-
B.
hasProduct
Indicates that an entity possesses, offers, or is associated with a particular product.
-
C.
hasRetailOption
Indicates that one entity offers, includes, or is associated with a particular retail option (such as a sales channel, purchase method, or retail configuration) for another entity.
-
D.
hasRetailProduct
Indicates that an entity offers, sells, or makes available a particular product in a retail context.
-
E.
hasProductAttribute
chosen
Indicates that a product is associated with a specific attribute describing one of its characteristics or properties.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4adc03481909e0f657db01e5bab |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:40 p.m.