Triple
T12133983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense Export Control and Compliance System |
E289004
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government system |
C3212
|
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. government system Context triple: [Defense Export Control and Compliance System, instanceOf, U.S. government system]
-
A.
system of government agencies
chosen
A system of government agencies is an organized network of public institutions, each with specific legal authority and responsibilities, that collectively implement laws, deliver services, and administer public policy on behalf of the state.
-
B.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
C.
branch of government
A branch of government is a major division of a state's governing system, such as the executive, legislative, or judicial branch, each with distinct powers and responsibilities designed to balance and limit authority.
-
D.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
E.
republican government
A republican government is a political system in which power resides with the people and their elected representatives, rather than a monarch, and is exercised according to the rule of law and a constitution.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:49 p.m.