Triple
T20377722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaker colonization movement |
E497737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious migration movement |
C1594
|
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: religious migration movement Context triple: [Quaker colonization movement, instanceOf, religious migration movement]
-
A.
religious migration
chosen
Religious migration is the movement of individuals or groups across regions or countries primarily motivated by religious beliefs, practices, persecution, or the search for greater religious freedom.
-
B.
religious conversion movement
A religious conversion movement is a collective effort or organized campaign aimed at persuading individuals or groups to adopt a new religious faith, denomination, or set of spiritual beliefs, often involving structured teachings, rituals, and community support.
-
C.
immigration movement
Immigration movement is the large-scale relocation of people across national borders driven by economic, political, social, or environmental factors, reshaping both origin and destination societies.
-
D.
religious revival movement
A religious revival movement is a collective effort, often marked by intense emotional expression and organized campaigns, aimed at renewing or spreading religious faith and practices within a community or society.
-
E.
religious mission
A religious mission is an organized effort by a faith community or institution to spread its beliefs, provide spiritual guidance, and often deliver social or humanitarian services to people beyond its existing membership.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:27 a.m.