Triple
T31802363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prüm Abbey |
E811774
|
entity |
| Predicate | imperialAbbeyFrom |
P156327
|
FINISHED |
| Object | 10th 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: 10th century | Statement: [Prüm Abbey, imperialAbbeyFrom, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imperialAbbeyFrom Context triple: [Prüm Abbey, imperialAbbeyFrom, 10th century]
-
A.
elevatedToImperialAbbey
chosen
Indicates that a religious abbey was granted the status of an Imperial Abbey, becoming directly subject to the authority of the emperor rather than to local or regional lords.
-
B.
formerCistercianAbbey
Indicates that something was once a Cistercian abbey but no longer holds that status.
-
C.
abbeyConsecrated
Indicates that an abbey has been formally dedicated and made sacred for religious use through a consecration ceremony.
-
D.
abbeyOriginCentury
Indicates the century in which an abbey was originally founded or established.
-
E.
hadAbbey
Indicates that an entity possessed, was associated with, or was the site of a particular abbey.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:42 p.m.