Triple
T7932195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Cloud Storage |
E184212
|
entity |
| Predicate | hasStorageClass |
P79848
|
FINISHED |
| Object | Standard |
—
|
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: Standard | Statement: [Google Cloud Storage, hasStorageClass, Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageClass Context triple: [Google Cloud Storage, hasStorageClass, Standard]
-
A.
isMajorStorageFor
Indicates that one entity serves as the primary or main storage location or repository for another entity.
-
B.
hasIceClass
Indicates that an object (typically a vessel or structure) is assigned a specific ice classification denoting its capability to operate in icy or ice-infested waters.
-
C.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
-
D.
hasFeatureClass
Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
-
E.
hasDocumentClass
Indicates that an entity is associated with, or categorized under, a specific class or type of document.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ace87f081908635769942645e78 |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.