Triple
T28351433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Naumburg-Zeitz |
E718108
|
entity |
| Predicate | bishopSeatMovedFrom |
P21663
|
FINISHED |
| Object | Zeitz |
—
|
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: Zeitz | Statement: [Bishopric of Naumburg-Zeitz, bishopSeatMovedFrom, Zeitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopSeatMovedFrom Context triple: [Bishopric of Naumburg-Zeitz, bishopSeatMovedFrom, Zeitz]
-
A.
episcopalSeeTransferredTo
Indicates that the authority or jurisdiction of a bishop’s episcopal see has been officially moved from one location or diocese to another.
-
B.
episcopalSeeTransferredFrom
chosen
Indicates that the location or jurisdiction of a bishop’s episcopal see has been moved from one place or authority to another.
-
C.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
D.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
E.
administrativeCenterMovedFrom
Indicates that the role of administrative center was previously located in one place and has been transferred or relocated from that original location to another.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c0aa2708190ad3b454c74dad15f |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:46 a.m.