Triple
T27868127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale |
E704411
|
entity |
| Predicate | cemeteryGravesMovedTo |
P60564
|
FINISHED |
| Object | Shap |
—
|
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: Shap | Statement: [Mardale, cemeteryGravesMovedTo, Shap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryGravesMovedTo Context triple: [Mardale, cemeteryGravesMovedTo, Shap]
-
A.
laterBurialsMovedTo
Indicates that burials that occurred at a later time were relocated from their original site to another place.
-
B.
convertedToPermanentCemetery
Indicates that a site or burial ground previously used in a temporary or different capacity has been formally designated and established as a permanent cemetery.
-
C.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
D.
numberOfGravesApproximate
Indicates that the stated count of graves is an estimated or approximate number rather than an exact figure.
-
E.
cemeteryOpened
Indicates that a cemetery began operating or was officially opened at a specific time.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f639493f8c819088bf8a9f586dfb7b |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:22 p.m.