Triple
T36009731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Spyridon Church (Corfu) |
E1041371
|
entity |
| Predicate | patronSaintOfLocation |
P172260
|
FINISHED |
| Object | Corfu |
—
|
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: Corfu | Statement: [Saint Spyridon Church (Corfu), patronSaintOfLocation, Corfu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronSaintOfLocation Context triple: [Saint Spyridon Church (Corfu), patronSaintOfLocation, Corfu]
-
A.
saintPatronageAssociatedWith
chosen
Indicates that a patronage relationship exists, where a saint is recognized as a special protector or advocate for a particular person, group, place, activity, or cause.
-
B.
locatedInCityWithPatronSaint
Indicates that an entity is situated in a city whose designated patron saint is a specific person.
-
C.
mainChurchPatron
Indicates that one entity serves as the primary patron or chief sponsoring supporter of a particular church.
-
D.
parishPatronSaint
Indicates that a particular saint is recognized as the patron saint of a given parish.
-
E.
coPatronSaint
Indicates that two or more saints share the role of patronage over the same place, group, or cause.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acb2bca08190acb3c310ada7a8d1 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.