Triple
T37932897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft 365 Family |
E946263
|
entity |
| Predicate | billingOption |
P36173
|
FINISHED |
| Object | monthly |
—
|
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 | Statement: [Microsoft 365 Family, billingOption, monthly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingOption Context triple: [Microsoft 365 Family, billingOption, monthly]
-
A.
billingMethod
chosen
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
-
B.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
C.
billType
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
D.
billCharacteristic
Indicates that a bill possesses or is associated with a particular characteristic or attribute.
-
E.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.