Triple
T32012975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mausoleum of Galla Placidia |
E817455
|
entity |
| Predicate | possibleBurialPlaceOf |
P118842
|
FINISHED |
| Object | Galla Placidia |
—
|
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: Galla Placidia | Statement: [Mausoleum of Galla Placidia, possibleBurialPlaceOf, Galla Placidia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleBurialPlaceOf Context triple: [Mausoleum of Galla Placidia, possibleBurialPlaceOf, Galla Placidia]
-
A.
burialPlace
Indicates the location where a person or entity is buried.
-
B.
reputedBurialPlaceOf
chosen
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
C.
buriedNear
Indicates that one entity is interred or buried in close physical proximity to another entity.
-
D.
burialSiteNear
Indicates that the burial site of one entity is located geographically close to another entity.
-
E.
locatedInTheAdministrativeTerritorialEntityOfBurial
Indicates that the place or site referenced is situated within the specified administrative territorial entity where the burial is located.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:15 a.m.