Triple
T10857201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methodist circuit in Lancashire |
E256297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious administrative unit |
C26089
|
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 administrative unit Context triple: [Methodist circuit in Lancashire, instanceOf, religious administrative unit]
-
A.
religious administrative center
A religious administrative center is an institution or complex where the organizational, bureaucratic, and leadership functions of a religious community or denomination are coordinated and managed.
-
B.
religious region
A religious region is a geographic area defined primarily by the prevalence, influence, or institutional presence of a particular religion or set of religious practices.
-
C.
religious province-level entity
chosen
A religious province-level entity is an administrative division within a religious organization that oversees and coordinates the activities, governance, and spiritual leadership of multiple subordinate units (such as dioceses, districts, or congregations) within a defined geographic area.
-
D.
administrative territorial entity
An administrative territorial entity is a geographically defined area governed by an authority that exercises administrative, political, or legal control within its boundaries.
-
E.
administrative district of Israel
An administrative district of Israel is a primary territorial division used by the Israeli government to organize local governance, public administration, and the delivery of state services.
- 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:20 p.m.