Triple
T28396692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoho Subscriptions |
E719302
|
entity |
| Predicate | supportsBillingFrequency |
P79845
|
FINISHED |
| Object | monthly billing |
—
|
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: monthly billing | Statement: [Zoho Subscriptions, supportsBillingFrequency, monthly billing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBillingFrequency Context triple: [Zoho Subscriptions, supportsBillingFrequency, monthly billing]
-
A.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
-
B.
supportsCodeRates
Indicates that one entity is capable of handling, processing, or operating at the specific code rates associated with another entity.
-
C.
hasStarBilling
Indicates that an entity is given top or prominently featured billing in a production or presentation.
-
D.
hasInstallment
Indicates that one entity is paid for or fulfilled through multiple scheduled installment payments by another entity.
-
E.
billingGranularity
chosen
Indicates the level of detail or unit (such as per item, per hour, or per month) at which charges are calculated and presented in billing.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: April 28, 2026, 1:17 a.m.