Triple
T5464274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osnabrück Cathedral |
E122666
|
entity |
| Predicate | firstBishopricEstablished |
P16622
|
FINISHED |
| Object | circa 780s |
—
|
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: circa 780s | Statement: [Osnabrück Cathedral, firstBishopricEstablished, circa 780s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBishopricEstablished Context triple: [Osnabrück Cathedral, firstBishopricEstablished, circa 780s]
-
A.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
B.
firstBishop
Indicates that one entity is the first bishop (earliest in time or rank) associated with or holding episcopal authority over another entity.
-
C.
foundedAsMissionaryDistrict
Indicates that an organization, typically a religious or ecclesiastical jurisdiction, was originally established in the form of a missionary district.
-
D.
establishedAsDiocese
chosen
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
E.
beganTermAsPresidingBishopOn
Indicates the date on which an individual started their term serving in the role of Presiding Bishop.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd927c946c8190aef40679199fede3 |
completed | March 20, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69bd91a370a88190b5d17b8a5387138d |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.