Triple
T18017495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowpipe |
E431031
|
entity |
| Predicate | loadBehavior |
P41759
|
FINISHED |
| Object | loads data as it arrives |
—
|
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: loads data as it arrives | Statement: [Snowpipe, loadBehavior, loads data as it arrives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadBehavior Context triple: [Snowpipe, loadBehavior, loads data as it arrives]
-
A.
loadBearingFor
Indicates that one entity structurally supports and carries the weight or load of another entity.
-
B.
readBehavior
Indicates that one entity engages in the act or manner of reading something, capturing how that reading is performed or characterized.
-
C.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
D.
loadType
chosen
Indicates the manner or category of how something is loaded, such as the method, configuration, or type of loading applied in a given context.
-
E.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9be5d0c819097e006f32d98753a |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.