Triple
T27612741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud computing |
E700366
|
entity |
| Predicate | majorProvider |
P58712
|
FINISHED |
| Object | Amazon Web Services |
—
|
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: Amazon Web Services | Statement: [Cloud computing, majorProvider, Amazon Web Services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorProvider Context triple: [Cloud computing, majorProvider, Amazon Web Services]
-
A.
isMajorProviderFor
chosen
Indicates that one entity serves as a primary or leading supplier or source of goods, services, or resources for another entity.
-
B.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
C.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
D.
typicalProvider
Indicates that one entity commonly or characteristically serves as a provider of goods, services, or resources to another entity.
-
E.
majorProvision
Indicates that one entity constitutes a primary or most significant part, feature, or component of another entity.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 27, 2026, 2:11 p.m.