Triple
T1248589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stafford Act |
E26822
|
entity |
| Predicate | policyStatementSection |
P22522
|
FINISHED |
| Object | 42 U.S.C. §5121 |
—
|
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: 42 U.S.C. §5121 | Statement: [Stafford Act, policyStatementSection, 42 U.S.C. §5121]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyStatementSection Context triple: [Stafford Act, policyStatementSection, 42 U.S.C. §5121]
-
A.
lawStatement
chosen
Indicates that an entity expresses, codifies, or articulates a legal rule, principle, or requirement.
-
B.
significantLawSection
Indicates that a particular section of law is especially relevant or important in the context of the described legal situation or relationship.
-
C.
policyImplication
Indicates that one policy, decision, or condition leads to, justifies, or necessitates another policy outcome or course of action.
-
D.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
E.
policyStance
Indicates the position or viewpoint an entity holds regarding a specific policy or set of policies.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf827e088190a16d845cea14f2c9 |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6b075881908e867c25b5080e25 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.