Triple
T20327932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox Ecclesiastical Mission in Jerusalem |
E492389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical mission |
C31515
|
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: ecclesiastical mission Context triple: [Russian Orthodox Ecclesiastical Mission in Jerusalem, instanceOf, ecclesiastical mission]
-
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.
Catholic mission
A Catholic mission is a religious outpost or organized effort established by the Catholic Church to evangelize, provide pastoral care, and offer social services to a specific community or region.
-
C.
mission church
A mission church is a religious building or congregation established by a parent church or missionary organization to serve a specific community, often in a developing or newly evangelized area.
-
D.
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.
-
E.
Russian Orthodox Church mission
chosen
A Russian Orthodox Church mission is a religious organization or outpost established to spread the Orthodox faith, provide pastoral care, and support spiritual, cultural, and charitable activities among local or diaspora communities under the jurisdiction of the Russian Orthodox Church.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:21 a.m.