Triple
T4326435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowpark |
E96643
|
entity |
| Predicate | runsWhere |
P23495
|
FINISHED |
| Object | inside Snowflake compute engine |
—
|
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: inside Snowflake compute engine | Statement: [Snowpark, runsWhere, inside Snowflake compute engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsWhere Context triple: [Snowpark, runsWhere, inside Snowflake compute engine]
-
A.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
B.
runsUnder
chosen
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
C.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
-
D.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
E.
runsBeneath
Indicates that one entity extends or moves below another entity along its length or span.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3513020f481909ff2fec3934f3002 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.