Triple
T4239220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Turku |
E94768
|
entity |
| Predicate | isSuffraganSeeOf |
P17915
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Diocese of Turku, isSuffraganSeeOf, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuffraganSeeOf Context triple: [Diocese of Turku, isSuffraganSeeOf, none]
-
A.
hasSuffraganDiocese
chosen
Indicates that one diocese is subordinate to and under the ecclesiastical jurisdiction of another diocese.
-
B.
hasSuffraganBishop
Indicates that one bishop holds the position of suffragan (subordinate or assistant) bishop in relation to another bishop or ecclesiastical authority.
-
C.
isTitularChurchOf
Indicates that a particular church holds the official honorary title associated with a specific cardinal or ecclesiastical office.
-
D.
isDiocesanSeatOf
Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
-
E.
hasApostolicSee
Indicates that a religious jurisdiction or entity is under the authority or oversight of a particular apostolic see (central episcopal seat).
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.