Triple
T418469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temporary Assistance for Needy Families |
E8045
|
entity |
| Predicate | canFund |
P154
|
FINISHED |
| Object | cash assistance payments |
—
|
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: cash assistance payments | Statement: [Temporary Assistance for Needy Families, canFund, cash assistance payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canFund Context triple: [Temporary Assistance for Needy Families, canFund, cash assistance payments]
-
A.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
B.
funds
chosen
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
C.
authorizesFundingFor
Indicates that one entity grants official approval or permission for financial resources to be provided to another entity or purpose.
-
D.
canAward
Indicates that one entity has the authority or ability to grant an award, honor, or recognition to another entity.
-
E.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd1ca148190a66bd8c5aad867d5 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.