Triple
T11117120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middelstum |
E262914
|
entity |
| Predicate | HippolytuskerkDenomination |
P61129
|
FINISHED |
| Object | Protestant church |
—
|
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: Protestant church | Statement: [Middelstum, HippolytuskerkDenomination, Protestant church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HippolytuskerkDenomination Context triple: [Middelstum, HippolytuskerkDenomination, Protestant church]
-
A.
denominationOfMainChurch
chosen
Indicates the religious denomination to which the main church of an entity belongs.
-
B.
principalChurchOf
Indicates that one church serves as the main or most important church associated with a particular entity, such as a region, denomination, or institution.
-
C.
parishChurchDenomination
Indicates the religious denomination with which a parish church is formally affiliated.
-
D.
establishedChurch
Indicates that a particular church is officially recognized and supported by the state as its formal or primary religious institution.
-
E.
hasCathedralDenomination
Indicates the religious denomination with which a cathedral is affiliated or to which it belongs.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af638b08190b7ade5eb0cab6b75 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.