Triple
T11401472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Traffic in Arms Regulations |
E270118
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | export control regime |
C19222
|
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: export control regime Context triple: [International Traffic in Arms Regulations, instanceOf, export control regime]
-
A.
export control authority
An export control authority is a governmental or regulatory body responsible for overseeing, licensing, and enforcing laws and regulations governing the transfer of controlled goods, technologies, and services across national borders.
-
B.
export control law
chosen
Export control law is the body of legal rules and regulations that govern the transfer of goods, technology, software, and services across national borders to protect national security, foreign policy interests, and international obligations.
-
C.
export control list
An export control list is an official catalog of goods, technologies, software, and services whose export is restricted or regulated by a government for reasons such as national security, foreign policy, or trade protection.
-
D.
administrative oversight regime
An administrative oversight regime is a structured system of rules, procedures, and institutions designed to monitor, review, and correct the actions and decisions of administrative bodies to ensure legality, accountability, and fairness.
-
E.
central control system
A central control system is a coordinating entity that monitors, manages, and directs the operations of interconnected components or subsystems to achieve overall system objectives.
- 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_69d6aacdbc6c8190af6dc3d5f5d22836 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:34 p.m.