Triple
T12476788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox missions |
E298194
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial religious enterprise |
C6370
|
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 religious enterprise Context triple: [Russian Orthodox missions, instanceOf, colonial religious enterprise]
-
A.
colonial enterprise
A colonial enterprise is an organized venture, typically led by a state or chartered company, that establishes control over foreign territories and peoples to extract resources, labor, and strategic advantage.
-
B.
colonial order
A colonial order is a hierarchical system of political, economic, and cultural domination in which an external power controls and structures the institutions, resources, and social relations of a colonized territory to serve imperial interests.
-
C.
colonial institutions
Colonial institutions are the formal and informal political, legal, economic, and social structures established by colonial powers to govern, extract resources from, and control colonized populations, often leaving long-lasting impacts on postcolonial societies.
-
D.
Puritan settlement
A Puritan settlement is a religiously motivated colonial community organized around strict moral codes, communal labor, and governance rooted in Puritan interpretations of Christianity.
-
E.
religious settlement
chosen
A religious settlement is a community established and organized primarily around shared religious beliefs, practices, and institutions, often including places of worship and communal living arrangements.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:56 p.m.