Triple
T24379260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Bamberg |
E614562
|
entity |
| Predicate | lastPrinceBishop |
P64967
|
FINISHED |
| Object | Georg Karl von Fechenbach |
—
|
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: Georg Karl von Fechenbach | Statement: [Prince-Bishopric of Bamberg, lastPrinceBishop, Georg Karl von Fechenbach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastPrinceBishop Context triple: [Prince-Bishopric of Bamberg, lastPrinceBishop, Georg Karl von Fechenbach]
-
A.
finalBishop
chosen
Indicates that an entity holds the position or role of the last or ultimate bishop in a given succession or context.
-
B.
hadPrinceBishop
Indicates that an entity was governed or overseen by a prince-bishop, combining secular and ecclesiastical authority.
-
C.
hasPreviousBishop
Indicates that one bishop previously held the same episcopal position or office as another bishop.
-
D.
hasBishop
Indicates that one entity possesses, is assigned, or is associated with a bishop in relation to another entity.
-
E.
hasFirstBishop
Indicates that an entity is associated with a specific bishop who is designated as its first bishop in a sequence or hierarchy.
- 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_69e2d7e362e481909e32fe4ef8269d4f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293da489c81909a7912b790be8b8a |
completed | April 29, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:02 a.m.