Triple
T29448794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesuit mission chain in Baja California |
E746923
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious mission network |
C7115
|
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 mission network Context triple: [Jesuit mission chain in Baja California, instanceOf, religious mission network]
-
A.
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.
-
B.
religious network
chosen
A religious network is a structured system of individuals, groups, and institutions connected by shared beliefs, practices, and organizational ties that facilitate the spread and maintenance of a religious tradition.
-
C.
missionary society
A missionary society is an organized religious group dedicated to planning, supporting, and carrying out missionary work, often including evangelism, education, and social services in domestic or foreign fields.
-
D.
Roman Catholic mission network
A Roman Catholic mission network is an organized system of churches, religious orders, and agencies that coordinate evangelization, pastoral care, education, and charitable works to spread and sustain the Catholic faith across different regions and cultures.
-
E.
Christian mission station
A Christian mission station is a settlement or compound established by missionaries to evangelize, provide religious instruction, and often offer education, medical care, and social services to a local community.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:30 p.m.