Triple
T27713864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb of Richard III |
E698764
|
entity |
| Predicate | liturgicalLocation |
P163942
|
FINISHED |
| Object | chancel of Leicester Cathedral |
—
|
LITERAL FINISHED |
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: chancel of Leicester Cathedral | Statement: [Tomb of Richard III, liturgicalLocation, chancel of Leicester Cathedral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liturgicalLocation Context triple: [Tomb of Richard III, liturgicalLocation, chancel of Leicester Cathedral]
-
A.
liturgicalCenter
Indicates that a place functions as the primary site for conducting and organizing liturgical or religious worship activities for a community.
-
B.
congregationalLocation
Indicates the place where a congregation or group regularly gathers or meets.
-
C.
placeOfConsecration
Indicates the specific place where a religious or ceremonial consecration of something or someone took place.
-
D.
liturgicalSetting
Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
-
E.
placeOfWorshipLocation
Indicates the location where a particular place of worship is situated or found.
- F. None of above. chosen
Provenance (4 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_69f6416fbf4081909b0913c337927fc4 |
completed | May 2, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
| PDg | Predicate description generation | batch_69f63fd4f7448190930c723ba7cfce62 |
completed | May 2, 2026, 6:17 p.m. |
Created at: April 27, 2026, 3:03 p.m.