Triple
T13505861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St Leonard’s Church, Hythe |
E321012
|
entity |
| Predicate | ossuaryLocation |
P110020
|
FINISHED |
| Object | ambulatory of the crypt |
—
|
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: ambulatory of the crypt | Statement: [St Leonard’s Church, Hythe, ossuaryLocation, ambulatory of the crypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ossuaryLocation Context triple: [St Leonard’s Church, Hythe, ossuaryLocation, ambulatory of the crypt]
-
A.
tombLocatedIn
Indicates that a particular tomb is situated within or at a specified location or place.
-
B.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
C.
excavatedTomb
Indicates that one entity has uncovered or dug out a tomb as part of an excavation process.
-
D.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
excavatedIn
Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
- 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.