Triple
T25696874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gascoyne-Cecil family |
E644343
|
entity |
| Predicate | hasTraditionalBurialPlace |
P166154
|
FINISHED |
| Object | St Etheldreda's Church, Hatfield |
—
|
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: St Etheldreda's Church, Hatfield | Statement: [Gascoyne-Cecil family, hasTraditionalBurialPlace, St Etheldreda's Church, Hatfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalBurialPlace Context triple: [Gascoyne-Cecil family, hasTraditionalBurialPlace, St Etheldreda's Church, Hatfield]
-
A.
hasBurialPlaceTradition
chosen
Indicates a relationship where a person or group is associated with a traditional or customary place of burial.
-
B.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
E.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 21, 2026, 8:37 p.m.