Triple
T6325500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.J.Res.114 |
E141852
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authorization for use of military force |
C18613
|
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: authorization for use of military force Context triple: [H.J.Res.114, instanceOf, authorization for use of military force]
-
A.
legal authorization for use of military force
chosen
A legal authorization for use of military force is a formal governmental or legislative approval that permits specified military actions under defined conditions, limits, and objectives.
-
B.
provision of the War Powers Resolution
A provision of the War Powers Resolution is a specific legal requirement or constraint within the statute that governs how and when the U.S. President may deploy armed forces and the procedures for congressional authorization, notification, and withdrawal.
-
C.
military intervention
Military intervention is the deliberate use or deployment of a state's armed forces in another state's territory or conflict to influence political, security, or humanitarian outcomes.
-
D.
U.S. national security directive
A U.S. national security directive is a formal, often classified, presidential instruction that establishes policies, objectives, and courses of action related to the nation’s security and foreign affairs.
-
E.
military mobilization
Military mobilization is the organized process by which a state prepares and deploys its armed forces and resources for war or national defense.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:29 p.m.