Triple
T3108374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Minden |
E64889
|
entity |
| Predicate | foundedAsBishopric |
P16622
|
FINISHED |
| Object | circa 8th century |
—
|
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 8th century | Statement: [Prince-Bishopric of Minden, foundedAsBishopric, circa 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsBishopric Context triple: [Prince-Bishopric of Minden, foundedAsBishopric, circa 8th century]
-
A.
hasBishopric
Indicates that an entity holds or is assigned a bishopric, i.e., the office, jurisdiction, or see of a bishop.
-
B.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
-
C.
establishedAsDiocese
chosen
Indicates that an ecclesiastical jurisdiction was formally created or elevated to the status of a diocese.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
foundedAsMissionaryDistrict
Indicates that an organization, typically a religious or ecclesiastical jurisdiction, was originally established in the form of a missionary district.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada29eacc88190a19c5ca8e53e3dca |
completed | March 8, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.