Triple
T7932022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloud Functions |
E184210
|
entity |
| Predicate | billingGranularity |
P79845
|
FINISHED |
| Object | per-invocation |
—
|
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: per-invocation | Statement: [Cloud Functions, billingGranularity, per-invocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingGranularity Context triple: [Cloud Functions, billingGranularity, per-invocation]
-
A.
billingMetric
Indicates a relationship where a specific metric or measure is used as the basis for calculating billing or charges between entities.
-
B.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
C.
budgetChargedOn
Indicates that a specific budget is debited or applied as the source of funds for a given cost, transaction, or activity.
-
D.
chargeDetail
Indicates a detailed specification of a financial charge, including its components, conditions, or breakdown within a transaction or billing context.
-
E.
timeTravelGranularity
Indicates the level of temporal precision or resolution at which time travel or time-based operations can occur between entities.
- 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:07 p.m.