Triple
T20120113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamberg Cathedral |
E490581
|
entity |
| Predicate | reconsecratedAfterFire |
P21434
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Bamberg Cathedral, reconsecratedAfterFire, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reconsecratedAfterFire Context triple: [Bamberg Cathedral, reconsecratedAfterFire, 13th century]
-
A.
consecratedBy
Indicates that one entity has been formally made sacred, dedicated, or set apart for religious use through a ritual or act performed by another entity.
-
B.
isRituallyRecreatedAt
Indicates that an event, object, or practice is symbolically or ceremonially re-enacted or reproduced during a specified ritual occasion or setting.
-
C.
deconsecrated
Indicates that something previously dedicated as sacred or religious has had that sacred status formally removed or revoked.
-
D.
reopenedForWorship
Indicates that a previously closed or inactive place of worship has been opened again for religious services or rituals.
-
E.
consecrated
chosen
Indicates that an entity has been formally dedicated or made sacred for a religious or holy purpose.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6673cfaac81909d6216f3e37c2439 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.