Triple
T28195507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Oxford Utilities |
E716434
|
entity |
| Predicate | billingResponsibility |
P138037
|
FINISHED |
| Object | utility billing for water services |
—
|
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: utility billing for water services | Statement: [City of Oxford Utilities, billingResponsibility, utility billing for water services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: billingResponsibility Context triple: [City of Oxford Utilities, billingResponsibility, utility billing for water services]
-
A.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
-
B.
billingEntity
chosen
Indicates the entity that is responsible for issuing or receiving bills or invoices in a transaction or service relationship.
-
C.
billCharacteristic
Indicates that a bill possesses or is associated with a particular characteristic or attribute.
-
D.
chargesWere
Indicates that specific accusations or legal charges existed or were formally brought against an entity at some point in time.
-
E.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642d17c688190838ecd2f002afc89 |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:27 p.m.