Triple
T300877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Removal policy of the United States |
E6195
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government policy |
C832
|
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: government policy Context triple: [Indian Removal policy of the United States, instanceOf, government policy]
-
A.
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.
-
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.
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.
-
D.
United States federal policy
chosen
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.
-
E.
central government
The central government is the primary national authority that exercises overarching political, legislative, and administrative control over a state, coordinating and regulating functions that affect the country as a whole.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.