Triple
T21551792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conservice |
E531778
|
entity |
| Predicate | typeOfBilling |
P21527
|
FINISHED |
| Object | third-party utility 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: third-party utility billing | Statement: [Conservice, typeOfBilling, third-party utility billing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBilling Context triple: [Conservice, typeOfBilling, third-party utility billing]
-
A.
billType
chosen
Indicates the classification or category assigned to a bill (such as its kind, purpose, or procedural type).
-
B.
billingMethod
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
-
C.
billingAuthorityType
Indicates the specific role or category of authority responsible for issuing or managing a bill in the relationship between the parties.
-
D.
billedBy
Indicates that one entity issues a bill or invoice to another entity for goods, services, or charges.
-
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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.