Triple
T33463411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernese Reformed Church |
E856981
|
entity |
| Predicate | churchGovernanceBody |
P6330
|
FINISHED |
| Object | synod |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: synod | Statement: [Bernese Reformed Church, churchGovernanceBody, synod]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: churchGovernanceBody Context triple: [Bernese Reformed Church, churchGovernanceBody, synod]
-
A.
churchBodyResponsible
Indicates that a particular church body holds responsibility or authority for overseeing, managing, or caring for another entity or activity.
-
B.
churchPolity
Indicates the form, structure, and governing system by which a church or religious community is organized and administered.
-
C.
churchName
Indicates that one entity is the name or official designation of a church associated with another entity.
-
D.
ecclesiasticalPolity
chosen
Indicates the form, structure, and governing system by which a religious or church organization is administered and its authority is distributed.
-
E.
churchCommunion
Indicates a relationship in which an individual or group participates in or is in fellowship with a particular church community or denomination.
- F. None of above.
Provenance (3 batches)
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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4d5269081909a5c6ba07ad90283 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.