Triple
T37399031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEK |
E928939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Protestant church federation |
C26626
|
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: Protestant church federation Context triple: [UEK, instanceOf, Protestant church federation]
-
A.
Protestant federation
chosen
A Protestant federation is an organized alliance of Protestant churches or denominations that collaborate to coordinate religious activities, represent shared interests, and promote common theological or social goals while maintaining their individual autonomy.
-
B.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a shared governance, worship life, and mission.
-
C.
United Protestant regional church
A United Protestant regional church is a Christian ecclesiastical body that unites multiple Protestant traditions within a defined geographic area under a common organizational and theological framework.
-
D.
Protestant congregation
A Protestant congregation is a local community of believers who gather regularly for worship, teaching, fellowship, and service in accordance with Protestant Christian doctrines and practices.
-
E.
federated church
A federated church is a single local congregation formed by the union of two or more distinct denominational bodies that worship and minister together while maintaining ties to their respective parent denominations.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.