Triple
T13505882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Leonard’s Church, Hythe |
E321012
|
entity |
| Predicate | ossuaryAccess |
P110021
|
FINISHED |
| Object | open to visitors at certain times |
—
|
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: open to visitors at certain times | Statement: [St Leonard’s Church, Hythe, ossuaryAccess, open to visitors at certain times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ossuaryAccess Context triple: [St Leonard’s Church, Hythe, ossuaryAccess, open to visitors at certain times]
-
A.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
B.
hasBurialVault
Indicates that an entity possesses or is associated with a specific burial vault used for interment or storage of remains.
-
C.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
D.
hasPartInMausoleum
Indicates that an entity is a component, section, or element contained within or forming part of a mausoleum.
-
E.
hasSarcophagusMaterial
Indicates that a sarcophagus is made from, or primarily composed of, a specified material.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.