Triple
T28351434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Naumburg-Zeitz |
E718108
|
entity |
| Predicate | bishopSeatMovedTo |
P78350
|
FINISHED |
| Object | Naumburg |
—
|
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: Naumburg | Statement: [Bishopric of Naumburg-Zeitz, bishopSeatMovedTo, Naumburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopSeatMovedTo Context triple: [Bishopric of Naumburg-Zeitz, bishopSeatMovedTo, Naumburg]
-
A.
episcopalSeeTransferredTo
chosen
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
Indicates that the location or jurisdiction of a bishop’s episcopal see has been moved from one place or authority to another.
-
C.
countySeatMovedTo
Indicates that the official county seat was relocated from one place to another.
-
D.
establishedAsCurrentDiocese
Indicates that an ecclesiastical jurisdiction was formally constituted or recognized in its present status as a diocese.
-
E.
bishopAppointed
Indicates that an individual has been formally appointed to the position or office of bishop by an authorized authority.
- 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_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 12:46 a.m.