Triple
T28469406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Naumburg-Zeitz |
E720390
|
entity |
| Predicate | bishopsWere |
P164849
|
FINISHED |
| Object | imperial princes |
—
|
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: imperial princes | Statement: [Diocese of Naumburg-Zeitz, bishopsWere, imperial princes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopsWere Context triple: [Diocese of Naumburg-Zeitz, bishopsWere, imperial princes]
-
A.
includesBishops
Indicates that one entity contains or has among its members one or more bishops.
-
B.
majorityOfBishopsFrom
Indicates that, within a given group or context, more than half of the bishops originate from or are associated with a specified place or source.
-
C.
includedBishopsFrom
Indicates that a group, document, or event contains or incorporates bishops originating from a specified source or location.
-
D.
hasDiocesanBishops
Indicates that a church, diocese, or ecclesiastical jurisdiction is served or overseen by one or more diocesan bishops.
-
E.
hasBishopsConference
Indicates that an entity is associated with or belongs to a particular bishops' conference.
- F. None of above. chosen
Provenance (4 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 2:47 a.m.