Triple
T37979375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 67-85 |
E947509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | appropriations authorization law |
C20686
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: appropriations authorization law Context triple: [Public Law 67-85, instanceOf, appropriations authorization law]
-
A.
appropriations act
chosen
An appropriations act is a law passed by a legislature that authorizes specific government expenditures, allocating funds to agencies, programs, or activities for a defined period and purpose.
-
B.
appropriations rider
An appropriations rider is a provision added to a government spending bill that directs, limits, or conditions how allocated funds may be used, often to achieve policy goals unrelated to the bill’s primary purpose.
-
C.
public finance legislation
Public finance legislation comprises the body of laws and regulations that govern how governments raise revenue, allocate expenditures, manage public debt, and oversee fiscal responsibility to achieve economic and social policy objectives.
-
D.
transportation funding authorization act
A transportation funding authorization act is a legislative measure that approves and allocates financial resources for the planning, construction, operation, and maintenance of transportation infrastructure and related programs over a specified period.
-
E.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
- F. None of above.
Provenance (1 batch)
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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.