Triple
T11364668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 104-193 |
E269171
|
entity |
| Predicate | shiftedFundingTo |
P72661
|
FINISHED |
| Object | block grants to states |
—
|
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: block grants to states | Statement: [Public Law 104-193, shiftedFundingTo, block grants to states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftedFundingTo Context triple: [Public Law 104-193, shiftedFundingTo, block grants to states]
-
A.
additionalFunding
Indicates that one entity provides or allocates extra financial resources beyond an initial or existing amount to another entity or project.
-
B.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
C.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
D.
capitalMoveTo
Indicates that the status of being a capital city is transferred from one location to another, marking a change in the official seat of government.
-
E.
fundingFocus
chosen
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.