Triple
T36800536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Płock |
E909307
|
entity |
| Predicate | typeOfDioceseHeaded |
P89989
|
FINISHED |
| Object | suffragan diocese |
—
|
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: suffragan diocese | Statement: [Bishop of Płock, typeOfDioceseHeaded, suffragan diocese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDioceseHeaded Context triple: [Bishop of Płock, typeOfDioceseHeaded, suffragan diocese]
-
A.
typeOfHeadOfChurch
Indicates the specific role or office held by the person who serves as the head of a particular church or religious organization.
-
B.
dioceseType
chosen
Indicates the specific ecclesiastical category or kind of diocese that an entity belongs to.
-
C.
isEcclesiasticalHeadOf
Indicates that one entity serves as the highest religious or church authority for another entity.
-
D.
dioceseBishop
Indicates that a person serves as the bishop (ecclesiastical leader) of a specified diocese.
-
E.
diocesanBishop
Indicates that one entity serves as the diocesan bishop—the chief ecclesiastical authority—responsible for the other entity (a particular diocese).
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a032b2285ac81908826f311a222c749 |
completed | May 12, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_6a032929b8b88190bf7d14d789b38aeb |
completed | May 12, 2026, 1:20 p.m. |
Created at: May 3, 2026, 4:12 p.m.