Triple
T21667452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dick Act reforms |
E534758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States federal military legislation |
C354
|
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: United States federal military legislation Context triple: [Dick Act reforms, instanceOf, United States federal military legislation]
-
A.
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.
-
B.
United States federal statute
chosen
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.
-
C.
military legal code
A military legal code is a formal system of laws and regulations that governs the conduct, discipline, rights, and obligations of members of the armed forces.
-
D.
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.
-
E.
naval legislation
Naval legislation comprises the body of laws, regulations, and international agreements that govern the operation, safety, security, and environmental impact of ships and maritime activities at sea and in ports.
- 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_69e0c46898008190aa618a4af55bd1ee |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:37 p.m.