Triple
T9707759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 48 |
E234942
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | emergency powers clause |
C24796
|
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: emergency powers clause Context triple: [Article 48, instanceOf, emergency powers clause]
-
A.
state of emergency authority
chosen
State of emergency authority is the legally granted power enabling designated government entities to temporarily suspend or modify normal procedures, rights, and regulations in response to extraordinary crises to protect public safety and order.
-
B.
emergency legislation
Emergency legislation is a special category of law enacted rapidly, often with expedited procedures and temporary scope, to address urgent or unforeseen crises requiring immediate governmental action.
-
C.
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.
-
D.
executive order
An executive order is a formal directive issued by a head of the executive branch, such as a president or governor, that manages operations of the government and has the force of law within the scope of existing statutory or constitutional authority.
-
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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.