Triple
T25141972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Etheldreda |
E629825
|
entity |
| Predicate | isBuriedAt |
P111116
|
FINISHED |
| Object | Ely Cathedral (former abbey site) |
—
|
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: Ely Cathedral (former abbey site) | Statement: [Saint Etheldreda, isBuriedAt, Ely Cathedral (former abbey site)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBuriedAt Context triple: [Saint Etheldreda, isBuriedAt, Ely Cathedral (former abbey site)]
-
A.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
-
B.
bodyBuriedAt
chosen
Indicates that the physical remains of an entity are interred or concealed at a specific location.
-
C.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for another entity.
-
D.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
E.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by another entity.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46849ab4081909a2278c535b5e5bc |
completed | May 1, 2026, 8:46 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:29 a.m.