Triple
T36237670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Creek–British relations |
E891417
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial-era relations |
C1073
|
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: colonial-era relations Context triple: [Creek–British relations, instanceOf, colonial-era relations]
-
A.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
B.
historical relationship
chosen
A historical relationship is a connection between people, groups, or entities that existed in the past and is understood through documented events, interactions, and their lasting impact over time.
-
C.
colonial-era organization
A colonial-era organization is a formal group or institution established during a period of colonial rule to administer, exploit, or manage political, economic, social, or cultural affairs in a colonized territory.
-
D.
colonial network
A colonial network is a system of interconnected territories, institutions, and power relations through which a colonial power organizes control, resource extraction, and cultural influence across its colonies.
-
E.
Indigenous–United States relations
Indigenous–United States relations encompass the historical and contemporary political, legal, social, and cultural interactions between Native American nations and the U.S. government, including treaties, conflicts, policies, and ongoing struggles for sovereignty and rights.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.