Triple
T36586748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archdiocese of Cebu |
E902539
|
entity |
| Predicate | originallySuffraganOf |
P81005
|
FINISHED |
| Object | Archdiocese of Manila |
E238161
|
NE 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: Archdiocese of Manila | Statement: [Archdiocese of Cebu, originallySuffraganOf, Archdiocese of Manila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallySuffraganOf Context triple: [Archdiocese of Cebu, originallySuffraganOf, Archdiocese of Manila]
-
A.
suffraganOf
chosen
Indicates that one ecclesiastical jurisdiction or bishop is subordinate to and under the authority of a particular metropolitan or archdiocesan see.
-
B.
formerDiocese
Indicates that an entity was once a diocese but no longer holds that diocesan status.
-
C.
formerBishopSeatOf
Indicates that a location once served as the official episcopal seat of a bishop but no longer holds that status.
-
D.
dioceseErectedOn
Indicates the date or point in time when a diocese was formally established or created.
-
E.
hasSuffraganBishop
Indicates that one bishop holds the position of suffragan (subordinate or assistant) bishop in relation to another bishop or ecclesiastical authority.
- F. None of above.
Provenance (4 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a380efb1c81908ee75cfa0224c654 |
completed | June 23, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.