Triple
T380801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Compact for Safe, Orderly and Regular Migration process |
E8674
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global policy-making process |
C1071
|
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: global policy-making process Context triple: [Global Compact for Safe, Orderly and Regular Migration process, instanceOf, global policy-making process]
-
A.
United States federal policy
United States federal policy is the body of laws, regulations, and official actions enacted or implemented by the federal government to address national issues and guide public and private behavior across the country.
-
B.
domestic policy program
A domestic policy program is a coordinated set of government actions and initiatives designed to address specific national issues and objectives within a country’s borders.
-
C.
international relations
chosen
International relations is the study and practice of how states and other global actors interact, cooperate, and conflict within the international system.
-
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.
United States foreign policy
United States foreign policy is the strategic framework of decisions, actions, and principles through which the U.S. government manages its political, economic, military, and diplomatic relations with other countries and international organizations.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.