Triple
T2437384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cedar Falls Utilities |
E53191
|
entity |
| Predicate | customerTypeServed |
P19115
|
FINISHED |
| Object | residential customers |
—
|
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: residential customers | Statement: [Cedar Falls Utilities, customerTypeServed, residential customers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerTypeServed Context triple: [Cedar Falls Utilities, customerTypeServed, residential customers]
-
A.
categoryOfPeopleServed
chosen
Indicates the type or group of people that are the primary recipients or beneficiaries of a service or activity.
-
B.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
hasCustomers
Indicates that an entity maintains a business relationship in which other entities purchase or receive its goods or services as customers.
-
D.
servesCustomer
Indicates that one entity provides service, assistance, or products to another entity in the role of a customer.
-
E.
professionServed
Indicates that an entity has performed work or provided services in a particular profession or occupational role.
- 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_69ab495b6dac8190ac82661aa1452222 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.