Triple
T26527760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Devon (English Courtenay branch) |
E670737
|
entity |
| Predicate | hasBurialPlaceTradition |
P166154
|
FINISHED |
| Object | Exeter Cathedral |
—
|
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: Exeter Cathedral | Statement: [Earl of Devon (English Courtenay branch), hasBurialPlaceTradition, Exeter Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBurialPlaceTradition Context triple: [Earl of Devon (English Courtenay branch), hasBurialPlaceTradition, Exeter Cathedral]
-
A.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
B.
hasPrimaryReligionOfBurials
Indicates that a group or community predominantly practices a particular religion in the context of its burial customs or rites.
-
C.
burialPractice
Indicates the customary methods, rituals, or procedures a group uses to bury or inter their dead.
-
D.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
E.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
- F. None of above. chosen
Provenance (4 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 1:33 a.m.