Triple
T21581703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Export Licensing (Part 748) |
E532538
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. federal regulatory provision |
C20083
|
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 regulatory provision Context triple: [Export Licensing (Part 748), instanceOf, U.S. federal regulatory provision]
-
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.
regulatory provision
chosen
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
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.
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.
-
E.
United States federal government action
A United States federal government action is any formal decision, policy, regulation, enforcement measure, or operation undertaken by a federal branch or agency under constitutional or statutory authority to influence public affairs or implement federal law.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:31 p.m.