Triple
T25198649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OD |
E631068
|
entity |
| Predicate | usesCloudTechnologyFrom |
P162084
|
FINISHED |
| Object | Microsoft Azure |
—
|
NE NERFINISHED |
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: Microsoft Azure | Statement: [OD, usesCloudTechnologyFrom, Microsoft Azure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCloudTechnologyFrom Context triple: [OD, usesCloudTechnologyFrom, Microsoft Azure]
-
A.
cloudBased
Indicates that something is hosted, delivered, or operates via cloud computing infrastructure rather than on local hardware.
-
B.
typeOfCloud
Indicates the specific category or classification of a cloud within a cloud-type taxonomy or system.
-
C.
supportsCloudModel
Indicates that one entity provides compatibility with, or operational backing for, a cloud-based model offered or used by another entity.
-
D.
hasHICloud
Indicates that an entity possesses or is associated with high-intensity (HI) cloud coverage or cloud-related conditions.
-
E.
cloudServiceName
Indicates the specific name assigned to a cloud-based service associated with an entity.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 12:51 p.m.