Triple
T27713926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Martin, Leicester |
E698765
|
entity |
| Predicate | hasRelicOrBurial |
P80843
|
FINISHED |
| Object | remains of Richard III of England |
—
|
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: remains of Richard III of England | Statement: [St Martin, Leicester, hasRelicOrBurial, remains of Richard III of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelicOrBurial Context triple: [St Martin, Leicester, hasRelicOrBurial, remains of Richard III of England]
-
A.
hasBuriedRemains
chosen
Indicates that one entity contains or is the location of the buried remains of another entity.
-
B.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
-
C.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
D.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
E.
hasBurialsOf
Indicates that a location or site contains or includes the burial places of certain individuals or groups.
- 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_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: April 27, 2026, 3:03 p.m.