Triple
T14811533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 337 of the Tariff Act of 1930 |
E348191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. federal statute provision |
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: U.S. federal statute provision Context triple: [Section 337 of the Tariff Act of 1930, instanceOf, U.S. federal statute provision]
-
A.
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.
-
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.
federal law
A federal law is a legally binding rule or statute enacted by a national government’s legislative body that applies uniformly across all states or regions within that nation.
-
E.
United States federal document
A United States federal document is an official record, form, publication, or communication created, issued, or maintained by a federal agency or branch of the U.S. government in the course of its authorized duties.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:46 a.m.