Triple
T18017566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virtual Warehouse (Snowflake) |
E431032
|
entity |
| Predicate | billedIn |
P102235
|
FINISHED |
| Object | Snowflake credits |
—
|
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: Snowflake credits | Statement: [Virtual Warehouse (Snowflake), billedIn, Snowflake credits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billedIn Context triple: [Virtual Warehouse (Snowflake), billedIn, Snowflake credits]
-
A.
billedFrom
Indicates that a bill, invoice, or charge originates from or is issued by a particular source or entity.
-
B.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
C.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
D.
moneyBillDefinedBy
Indicates that a money bill is formally specified, characterized, or established by a particular source, document, or authority.
-
E.
payableIn
chosen
Indicates that a specified amount, obligation, or transaction must be settled using a particular currency, asset, or payment medium.
- 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_69e4b9bf85c08190a40cef4c6d7b566a |
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.