Triple
T26255308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LIHEAP |
E656698
|
entity |
| Predicate | typicalAssistanceForm |
P10121
|
FINISHED |
| Object | payment to utility company |
—
|
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: payment to utility company | Statement: [LIHEAP, typicalAssistanceForm, payment to utility company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAssistanceForm Context triple: [LIHEAP, typicalAssistanceForm, payment to utility company]
-
A.
typicalForm
Indicates that one entity represents the standard, characteristic, or most common form or shape in which another entity typically appears or is realized.
-
B.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of another entity.
-
C.
assistance
Indicates providing help, support, or aid from one entity to another to facilitate a task, goal, or need.
-
D.
assistanceMayInclude
Indicates that one entity’s assistance to another can optionally encompass or involve a specified type, component, or aspect of help.
-
E.
benefitForm
chosen
Indicates that one entity is a specific form, type, or variant in which a benefit is provided or realized for another entity.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 26, 2026, 9:08 p.m.