Triple
T1240061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authorization for Use of Military Force of 2001 |
E26637
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war powers authorization |
C202
|
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: war powers authorization Context triple: [Authorization for Use of Military Force of 2001, instanceOf, war powers authorization]
-
A.
Act of Congress
chosen
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.
-
B.
Cold War–era legislation
Cold War–era legislation encompasses laws and policies enacted primarily between the late 1940s and early 1990s that aimed to contain communism, regulate national security and intelligence activities, manage nuclear arms and defense spending, and shape domestic and foreign affairs in response to U.S.–Soviet geopolitical rivalry.
-
C.
United States House resolution
A United States House resolution is a formal legislative measure introduced and considered solely by the House of Representatives to express opinions, make internal rules, or address matters affecting only the House, without the force of law.
-
D.
war address
A war address is a formal speech delivered by a political or military leader during wartime to justify conflict, rally support, and shape public perception of the war effort.
-
E.
executive authority
Executive authority is the power and responsibility to implement, enforce, and administer laws and policies within a governing system or organization.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.