Triple
T25631345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomeranian Evangelical Church |
E642584
|
entity |
| Predicate | hadBishop |
P10284
|
FINISHED |
| Object | Hans-Jürgen Abromeit |
—
|
NE NERFINISHED |
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: Hans-Jürgen Abromeit | Statement: [Pomeranian Evangelical Church, hadBishop, Hans-Jürgen Abromeit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBishop Context triple: [Pomeranian Evangelical Church, hadBishop, Hans-Jürgen Abromeit]
-
A.
hasBishop
chosen
Indicates that one entity possesses, is assigned, or is associated with a bishop in relation to another entity.
-
B.
hasPreviousBishop
Indicates that one bishop previously held the same episcopal position or office as another bishop.
-
C.
hasFirstBishop
Indicates that an entity is associated with a specific bishop who is designated as its first bishop in a sequence or hierarchy.
-
D.
finalBishop
Indicates that an entity holds the position or role of the last or ultimate bishop in a given succession or context.
-
E.
hasBishopStyle
Indicates that an entity possesses or is characterized by a particular style or manner associated with a bishop.
- 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_69e77e7bd4548190a0c691b8a2f27ff1 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fa5dd31481909bfcbb9975403cc5 |
completed | May 2, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:18 p.m.