Triple
T24013013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of the Twelve Holy Apostles, Rome |
E594589
|
entity |
| Predicate | hasFuneraryMonumentOf |
P78565
|
FINISHED |
| Object | Pope Clement XIV |
—
|
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: Pope Clement XIV | Statement: [Basilica of the Twelve Holy Apostles, Rome, hasFuneraryMonumentOf, Pope Clement XIV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFuneraryMonumentOf Context triple: [Basilica of the Twelve Holy Apostles, Rome, hasFuneraryMonumentOf, Pope Clement XIV]
-
A.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
B.
hasGraveOrMemorialOf
chosen
Indicates that a location or object serves as the grave or memorial site dedicated to a particular person or entity.
-
C.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
D.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
E.
burialPlace
Indicates the location where a person or entity is buried.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d59ee0a08190ad1e1bc2dad1dda7 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:41 p.m.