Triple
T5794241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelter Plus Care program |
E128467
|
entity |
| Predicate | policyChangeEffective |
P49366
|
FINISHED |
| Object | HEARTH Act implementation |
—
|
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: HEARTH Act implementation | Statement: [Shelter Plus Care program, policyChangeEffective, HEARTH Act implementation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyChangeEffective Context triple: [Shelter Plus Care program, policyChangeEffective, HEARTH Act implementation]
-
A.
tookEffect
chosen
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
B.
policyShift
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
C.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
D.
effectiveFor
Indicates that one entity successfully produces the intended effect, benefit, or desired outcome for another entity or condition.
-
E.
hasLegalChange
Indicates that an entity has undergone or is associated with a modification in its legal status, rights, obligations, or regulatory conditions.
- 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_69c00845ca68819081a2ce3ecca577f7 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1304588190b59a18fb7b70a60f |
completed | March 22, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.