Triple
T34979580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Verden |
E1008776
|
entity |
| Predicate | bishopWas |
P182468
|
FINISHED |
| Object | Imperial prince |
—
|
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 prince | Statement: [Roman Catholic Diocese of Verden, bishopWas, Imperial prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopWas Context triple: [Roman Catholic Diocese of Verden, bishopWas, Imperial prince]
-
A.
bishopWhoRecognized
Indicates that a bishop acknowledged, identified, or formally recognized a particular person, group, status, or event.
-
B.
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).
-
C.
bishopInChargeAtConstruction
Indicates that a particular bishop held primary ecclesiastical authority over a church or religious building at the time it was constructed.
-
D.
bishopAppointed
Indicates that an individual has been formally appointed to the position or office of bishop by an authorized authority.
-
E.
bishopsWere
Indicates that certain entities held the position or role of bishops during a specified time or context.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.