Triple
T27713851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Richard III |
E698764
|
entity |
| Predicate | reinterredFrom |
P60564
|
FINISHED |
| Object | Greyfriars, Leicester |
—
|
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: Greyfriars, Leicester | Statement: [Tomb of Richard III, reinterredFrom, Greyfriars, Leicester]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinterredFrom Context triple: [Tomb of Richard III, reinterredFrom, Greyfriars, Leicester]
-
A.
reburialDate
Indicates the date on which something that was previously buried is buried again.
-
B.
reburialCoincidesWith
Indicates that the act of reburial occurs at the same time or within the same event or phase as another specified occurrence.
-
C.
originalBurialSiteOfRemainsLaterMovedTo
chosen
Indicates that a location was the initial burial site of human remains that were subsequently relocated to another place.
-
D.
hasReinterredPerson
Indicates that an entity has performed the act of reinterring (burying again) a particular person.
-
E.
laterBurialsMovedTo
Indicates that burials that occurred at a later time were relocated from their original site to another place.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635cdcff881908a30d6b18c2085f4 |
completed | May 2, 2026, 5:35 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:03 p.m.