Triple
T36362434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benevento (unmarked grave, traditionally) |
E895530
|
entity |
| Predicate | burialOfPersonRole |
P172814
|
FINISHED |
| Object | medieval monarch |
—
|
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: medieval monarch | Statement: [Benevento (unmarked grave, traditionally), burialOfPersonRole, medieval monarch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burialOfPersonRole Context triple: [Benevento (unmarked grave, traditionally), burialOfPersonRole, medieval monarch]
-
A.
hasBuriedPersonRole
chosen
Indicates that an entity plays a specific role in the context of a person who has been buried (e.g., as the buried individual or in relation to the burial).
-
B.
burialBy
Indicates that one entity is responsible for burying or interring another entity.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
burialDetail
Indicates details about how, where, and under what circumstances an entity is buried.
-
E.
burialText
Indicates that a text is inscribed on, associated with, or used in connection with a burial or funerary context.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.