Triple
T825621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowflake |
E17845
|
entity |
| Predicate | hasArchitecture |
P4631
|
FINISHED |
| Object | multi-cluster shared data architecture |
—
|
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: multi-cluster shared data architecture | Statement: [Snowflake, hasArchitecture, multi-cluster shared data architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchitecture Context triple: [Snowflake, hasArchitecture, multi-cluster shared data architecture]
-
A.
hasArchitecturalFeature
Indicates that one entity possesses, includes, or is characterized by a specific architectural feature or element.
-
B.
graphicsArchitecture
Indicates the underlying design or structural framework that defines how a system’s graphics or visual rendering components are organized and operate.
-
C.
cpuArchitecture
Indicates the type of processor instruction set or hardware architecture that a computing system or component is designed to run on.
-
D.
hasInfrastructureType
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
E.
architectureType
chosen
Indicates the specific style or category of architecture that characterizes or defines an 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_69a4937c9c188190aaa216f6b466f452 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ab976094819086d676404d745750 |
completed | March 1, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69a4aa781e1081909df006f730296c53 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.