Triple
T29112647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Uroš V |
E736953
|
entity |
| Predicate | burialRelocation |
P40366
|
FINISHED |
| Object | relics translated to Jazak Monastery in Fruška Gora |
—
|
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: relics translated to Jazak Monastery in Fruška Gora | Statement: [Stefan Uroš V, burialRelocation, relics translated to Jazak Monastery in Fruška Gora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialRelocation Context triple: [Stefan Uroš V, burialRelocation, relics translated to Jazak Monastery in Fruška Gora]
-
A.
laterBurialsMovedTo
chosen
Indicates that burials that occurred at a later time were relocated from their original site to another place.
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
originalBurialSiteOfRemainsLaterMovedTo
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
D.
reburialCoincidesWith
Indicates that the act of reburial occurs at the same time or within the same event or phase as another specified occurrence.
-
E.
reburialDate
Indicates the date on which something that was previously buried is buried again.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661ed89f08190a52d68a08a0be6bb |
completed | May 2, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:19 a.m.