Triple
T4669327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winchester Cathedral |
E102922
|
entity |
| Predicate | containsMortuaryChestsOf |
P58747
|
FINISHED |
| Object | Anglo-Saxon kings of Wessex |
—
|
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: Anglo-Saxon kings of Wessex | Statement: [Winchester Cathedral, containsMortuaryChestsOf, Anglo-Saxon kings of Wessex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMortuaryChestsOf Context triple: [Winchester Cathedral, containsMortuaryChestsOf, Anglo-Saxon kings of Wessex]
-
A.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
B.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
-
C.
hasBurialsFrom
Indicates that a location or site contains burials originating from a specified time period, culture, or source.
-
D.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
E.
hasGraveGoods
Indicates that a burial or grave contains associated objects or goods placed with the deceased.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd655719dc8190beb6942f343a0ae7 |
completed | March 20, 2026, 3:18 p.m. |
Created at: March 20, 2026, 1:15 p.m.