Triple
T33849905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Catholic Diocese of Auki |
E867592
|
entity |
| Predicate | bishopOrdinary |
P76681
|
FINISHED |
| Object | Peter Houhou |
—
|
NE NERFINISHED |
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: Peter Houhou | Statement: [Roman Catholic Diocese of Auki, bishopOrdinary, Peter Houhou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bishopOrdinary Context triple: [Roman Catholic Diocese of Auki, bishopOrdinary, Peter Houhou]
-
A.
diocesanBishop
chosen
Indicates that one entity serves as the diocesan bishop—the chief ecclesiastical authority—responsible for the other entity (a particular diocese).
-
B.
bishopricNow
Indicates that an entity currently holds or occupies the office or position of bishop over a particular diocese or jurisdiction.
-
C.
bishopricCreated
Indicates that a bishopric (an ecclesiastical jurisdiction or office of a bishop) has been formally established or created.
-
D.
bishopAppointed
Indicates that an individual has been formally appointed to the position or office of bishop by an authorized authority.
-
E.
consecratedAsBishopIn
Indicates that a person was formally ordained and installed as a bishop within a specified place, diocese, or jurisdiction.
- 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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700714a908190ba78a2e5ac4c0261 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.