Triple
T1207457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Militia Acts of the United States |
E25921
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | series of federal statutes |
C251
|
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: series of federal statutes Context triple: [Militia Acts of the United States, instanceOf, series of federal statutes]
-
A.
United States federal statute
A United States federal statute is a law formally enacted by Congress and signed by the President (or passed over a veto) that applies nationwide and governs conduct, rights, and obligations under federal jurisdiction.
-
B.
United States federal law
United States federal law is the body of statutes, regulations, and legal principles enacted or authorized by the federal government that governs nationwide matters under the U.S. Constitution.
-
C.
United States federal law instrument
A United States federal law instrument is an official legal document or mechanism, such as a statute, regulation, executive order, or treaty, through which the federal government creates, modifies, or enforces legal obligations and rights.
-
D.
constitutional statute
A constitutional statute is a fundamental law enacted by a legislature that, while formally an ordinary statute, has quasi-constitutional status because it implements, structures, or protects core constitutional principles and cannot be amended or repealed without special procedures or heightened scrutiny.
-
E.
statute
chosen
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:46 p.m.