Triple
T38065418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church Representation Rules of the Church of England |
E950457
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canonical regulation |
C9616
|
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: canonical regulation Context triple: [Church Representation Rules of the Church of England, instanceOf, canonical regulation]
-
A.
canonical legislation
chosen
Canonical legislation is the body of laws and regulations established by ecclesiastical authority to govern the doctrine, discipline, and administration of a religious institution, particularly within the Christian tradition.
-
B.
internal regulation
Internal regulation is the set of processes and mechanisms by which a system monitors and adjusts its own internal states and activities to maintain stability and achieve its goals.
-
C.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
D.
regulations
Regulations are authoritative rules or directives established by a governing body to control, manage, or guide behaviors and processes within a specific domain.
-
E.
regulatory activity
Regulatory activity is the process by which an entity establishes, interprets, or enforces rules and standards to guide or control the behavior of systems, organizations, or individuals.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.