Triple
T29841979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esbo stift |
E757824
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Diocese of Espoo |
C15393
|
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: Diocese of Espoo Context triple: [Esbo stift, instanceOf, Diocese of Espoo]
-
A.
Lutheran diocese
chosen
A Lutheran diocese is an administrative and ecclesiastical district of the Lutheran Church, overseen by a bishop and comprising multiple congregations within a defined geographic area.
-
B.
Finnish bishop
A Finnish bishop is a high-ranking clergy member of the Evangelical Lutheran Church of Finland (or other Christian denominations in Finland) responsible for overseeing a diocese, guiding clergy and laity, and representing the church in religious and public life.
-
C.
district of Espoo
A district of Espoo is an administrative and geographical subdivision of the city of Espoo, Finland, defined for local governance, planning, and statistical purposes.
-
D.
missionary diocese
A missionary diocese is a territorial ecclesiastical jurisdiction, often in a developing or non-traditional Christian region, established to organize and advance the church’s missionary, pastoral, and evangelizing work under the authority of a bishop or equivalent leader.
-
E.
district of Helsinki
A district of Helsinki is an administrative and geographical subdivision of Finland’s capital city, defined for governance, planning, and statistical purposes, typically comprising several neighborhoods with shared services and infrastructure.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 5:39 p.m.