Triple
T29772749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Conference of the United Methodist Church |
E755291
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | denominational legislative assembly |
C26812
|
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: denominational legislative assembly Context triple: [General Conference of the United Methodist Church, instanceOf, denominational legislative assembly]
-
A.
denominational body
chosen
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
B.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
C.
denominational constitution
A denominational constitution is a formal governing document that defines the beliefs, organizational structure, authority, and operational rules of a religious denomination.
-
D.
subnational legislature
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
E.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 8:43 p.m.