Triple
T5217222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Paul's Cathedral memorial, London (cenotaph) |
E117781
|
entity |
| Predicate | hasMemorialForm |
P7960
|
FINISHED |
| Object | empty tomb |
—
|
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: empty tomb | Statement: [St Paul's Cathedral memorial, London (cenotaph), hasMemorialForm, empty tomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemorialForm Context triple: [St Paul's Cathedral memorial, London (cenotaph), hasMemorialForm, empty tomb]
-
A.
hasMemorial
Indicates that a memorial exists in honor of, or dedicated to, a particular entity.
-
B.
hasAdjacentMemorial
Indicates that one memorial is located directly next to or in close proximity to another memorial.
-
C.
memorialType
chosen
Indicates the specific kind or category of memorial associated with an entity (e.g., plaque, statue, monument).
-
D.
hasCommemorationFunction
Indicates that something serves the role or purpose of commemorating an event, person, group, or concept.
-
E.
memorialization
Indicates the act of preserving the memory or honoring the legacy of someone or something, often through a dedicated object, event, or practice.
- 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_69bd4465e03081909bfcfd7113062590 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a95abdc8190b0babd79cea1360e |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bd2a448190a9ae5afd2585a7b9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.