Triple
T25731587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Łódź |
E645255
|
entity |
| Predicate | metropolitanArchbishopStart |
P16624
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Archdiocese of Łódź, metropolitanArchbishopStart, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metropolitanArchbishopStart Context triple: [Archdiocese of Łódź, metropolitanArchbishopStart, 2017]
-
A.
archbishopOf
Indicates that a person holds the ecclesiastical office of archbishop in relation to a specific diocese, region, or church jurisdiction.
-
B.
currentArchbishopStartYear
chosen
Indicates the calendar year in which the current archbishop began serving in that role.
-
C.
metropolitanArchdioceseOf
Indicates that one ecclesiastical jurisdiction is the metropolitan archdiocese that has authority over another church territory or diocese.
-
D.
archbishopricPredecessor
Indicates that one entity previously held the position of archbishop immediately before another entity in the same archbishopric office.
-
E.
hasMetropolitanBishop
Indicates that a given ecclesiastical jurisdiction is under the authority or oversight of a specific metropolitan bishop.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbbd6a081908cb31bba20397f57 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 11:16 p.m.