Triple
T106358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Act Amendments of 1949 |
E2145
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | amendment to the National Security Act of 1947 |
C3756
|
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: amendment to the National Security Act of 1947 Context triple: [National Security Act Amendments of 1949, instanceOf, amendment to the National Security Act of 1947]
-
A.
amendment to the United States Constitution
An amendment to the United States Constitution is a formally adopted change or addition to the Constitution’s text that alters, clarifies, or expands the nation’s fundamental legal framework.
-
B.
constitutional amendment
A constitutional amendment is a formal, legally prescribed change or addition to a constitution that alters its text, meaning, or application.
-
C.
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.
-
D.
clause of the United States Constitution
A clause of the United States Constitution is a distinct, self-contained provision within the document that establishes specific powers, rights, limitations, or procedures governing the federal government and its relationship to the states and the people.
-
E.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
- F. None of above. chosen
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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.