Triple
T29306128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mausoleum of Theoderic in Ravenna |
E743099
|
entity |
| Predicate | originalBurial |
P60564
|
FINISHED |
| Object | Theoderic the Great |
—
|
NE NERFINISHED |
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: Theoderic the Great | Statement: [Mausoleum of Theoderic in Ravenna, originalBurial, Theoderic the Great]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalBurial Context triple: [Mausoleum of Theoderic in Ravenna, originalBurial, Theoderic the Great]
-
A.
firstBurial
Indicates that an entity is the earliest or initial burial associated with a person, place, or burial context.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
D.
possiblyBurialOf
Indicates that one entity is a potential or uncertain burial site, grave, or interment location associated with another entity.
-
E.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by another entity.
- 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_69f09123ed9881909f351f7541933f5e |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: April 28, 2026, 1:13 p.m.