Triple
T23473918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | José Horacio Gómez |
E570206
|
entity |
| Predicate | startDateAsAuxiliaryBishopOfDenver |
P15396
|
FINISHED |
| Object | 2001-03-26 |
—
|
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: 2001-03-26 | Statement: [José Horacio Gómez, startDateAsAuxiliaryBishopOfDenver, 2001-03-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateAsAuxiliaryBishopOfDenver Context triple: [José Horacio Gómez, startDateAsAuxiliaryBishopOfDenver, 2001-03-26]
-
A.
consecratedAsBishopDate
Indicates the date on which an individual was formally consecrated to the office of bishop.
-
B.
startTimeAsCoadjutorBishopOfDaejeon
Indicates the date and time when an individual began serving as the coadjutor bishop of the Diocese of Daejeon.
-
C.
beganTermAsPresidingBishopOn
Indicates the date on which an individual started their term serving in the role of Presiding Bishop.
-
D.
appointedAuxiliaryBishop
chosen
Indicates that one entity formally assigns another to serve in the role of auxiliary bishop within a diocese or ecclesiastical jurisdiction.
-
E.
startTimeAsArchbishopOfBoston
Indicates the date and time when an individual began serving in the role of Archbishop of Boston.
- 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_69f1a70363488190bcbdedec5c2a945c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:59 p.m.