Triple
T24559930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Abbacy of Kempten |
E607622
|
entity |
| Predicate | elevatedToImperialAbbey |
P156327
|
FINISHED |
| Object | 9th 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: 9th century | Statement: [Prince-Abbacy of Kempten, elevatedToImperialAbbey, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToImperialAbbey Context triple: [Prince-Abbacy of Kempten, elevatedToImperialAbbey, 9th century]
-
A.
elevatedToRoyalAbbey
Indicates that a religious institution was formally granted the status and privileges of a royal abbey by a monarch or ruling authority.
-
B.
elevatedToBasilica
Indicates that a church has been formally raised in status and designated as a basilica by ecclesiastical authority.
-
C.
elevatedToEparchyFrom
Indicates that a religious jurisdiction was raised in status to an eparchy from a specified prior ecclesiastical unit or rank.
-
D.
elevatedToArchdioceseBy
Indicates that one ecclesiastical jurisdiction was raised in rank to an archdiocese by a particular authority or decision.
-
E.
elevatedToArcheparchy
Indicates that a church jurisdiction or eparchy has been raised in rank or status to that of an archeparchy.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f57a7c8190a0eb8d6d6ef6ae61 |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
| PDg | Predicate description generation | batch_69f2a846c5bc81909ba50cee483bea91 |
completed | April 30, 2026, 12:54 a.m. |
Created at: April 18, 2026, 2:27 a.m.