Triple
T31042844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Worms |
E791041
|
entity |
| Predicate | bishopHeldTitle |
P26255
|
FINISHED |
| Object | Prince-Bishop of Worms |
—
|
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: Prince-Bishop of Worms | Statement: [Diocese of Worms, bishopHeldTitle, Prince-Bishop of Worms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopHeldTitle Context triple: [Diocese of Worms, bishopHeldTitle, Prince-Bishop of Worms]
-
A.
usesArchiepiscopalTitle
Indicates that an entity employs an archiepiscopal (archbishop-level) ecclesiastical title in its official style or designation.
-
B.
currentArchbishopTitle
Indicates the official ecclesiastical title currently held by the person serving as archbishop of a given see or jurisdiction.
-
C.
diocesanBishopTitle
chosen
Indicates the formal ecclesiastical title held by a bishop who has jurisdiction over a diocese.
-
D.
bishopWhoRecognized
Indicates that a bishop acknowledged, identified, or formally recognized a particular person, group, status, or event.
-
E.
bishopIsExOfficio
Indicates that a person holds the position of bishop by virtue of holding another office or role (i.e., automatically, as an ex officio capacity).
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694fb85f881909734cf13cea84c78 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.