Triple
T23478641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Debrecen–Nyíregyháza |
E570337
|
entity |
| Predicate | dateCurrentBishopTookOffice |
P113333
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Roman Catholic Diocese of Debrecen–Nyíregyháza, dateCurrentBishopTookOffice, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateCurrentBishopTookOffice Context triple: [Roman Catholic Diocese of Debrecen–Nyíregyháza, dateCurrentBishopTookOffice, 2015]
-
A.
dateCurrentBishopInstalled
Indicates the date on which the current bishop officially assumed or was installed into office.
-
B.
electionYearOfCurrentBishop
Indicates the year in which the currently serving bishop was elected to their position.
-
C.
consecrationYearOfCurrentBishop
Indicates the year in which the current bishop associated with an entity was consecrated.
-
D.
currentBishop
Indicates that one entity currently holds the position or role of bishop with respect to another entity (such as a diocese or church).
-
E.
currentBishopStartYear
chosen
Indicates the year in which the current bishop began serving in their episcopal role.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a74e7e648190b89006dce7d7ce05 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:02 p.m.