Triple
T33323553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Tanwg |
E853202
|
entity |
| Predicate | hasMainPlaceOfVeneration |
P21389
|
FINISHED |
| Object | St Tanwg's Church, Harlech |
—
|
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 Tanwg's Church, Harlech | Statement: [Saint Tanwg, hasMainPlaceOfVeneration, St Tanwg's Church, Harlech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPlaceOfVeneration Context triple: [Saint Tanwg, hasMainPlaceOfVeneration, St Tanwg's Church, Harlech]
-
A.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
B.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
C.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
-
D.
hasMajorShrine
chosen
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
E.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00d820a7788190a8d54625cd87be68 |
completed | May 10, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_6a00d7c5b40c8190b80413238d04e81e |
completed | May 10, 2026, 7:08 p.m. |
Created at: May 1, 2026, 1:33 a.m.