Triple
T23854903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monks Risborough |
E592276
|
entity |
| Predicate | dedicatedChurchTo |
P138879
|
FINISHED |
| Object | St Dunstan |
—
|
NE NERFINISHED |
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: St Dunstan | Statement: [Monks Risborough, dedicatedChurchTo, St Dunstan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedChurchTo Context triple: [Monks Risborough, dedicatedChurchTo, St Dunstan]
-
A.
liturgicalDedication
Indicates that something (typically a religious building, object, or time) is formally dedicated or consecrated for use in a specific liturgical or worship context.
-
B.
religiousBuildingDedicatedTo
Indicates that a religious building is formally dedicated or consecrated to a particular deity, figure, or religious concept.
-
C.
isDevotedTo
Indicates a strong, enduring commitment or dedication that one entity directs toward another.
-
D.
hasParishChurchDedication
Indicates that a parish church is dedicated to, or placed under the patronage of, a particular figure, saint, or sacred concept.
-
E.
monasteryDedicatedTo
chosen
Indicates that a monastery is formally devoted or consecrated to a particular deity, saint, religious figure, or sacred concept.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c98a60b081908dbdc359f51e67fa |
completed | April 29, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:11 p.m.