Triple
T4502813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London area scheme |
E101262
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | church administrative structure |
C9797
|
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: church administrative structure Context triple: [London area scheme, instanceOf, church administrative structure]
-
A.
form of church polity
A form of church polity is a specific organizational structure and system of governance that defines how authority, decision-making, and leadership are distributed and exercised within a Christian church or denomination.
-
B.
form of church polity
chosen
A form of church polity is a conceptual structure that defines how authority, decision-making, and governance are organized and exercised within a Christian church or denomination.
-
C.
religious structure
A religious structure is a building or space specifically designed and used for worship, rituals, and other activities associated with a particular faith or spiritual tradition.
-
D.
ecclesiastical institution
An ecclesiastical institution is an organized religious body or establishment, such as a church or denomination, that governs and administers spiritual, liturgical, and doctrinal affairs within a faith tradition.
-
E.
institution of the Episcopal Church
An institution of the Episcopal Church is an organized body, such as a parish, diocese, school, or agency, that operates under the authority, doctrine, and governance structures of the Episcopal Church to carry out its religious, educational, or charitable mission.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:01 p.m.