Triple

T22523112
Position Surface form Disambiguated ID Type / Status
Subject Synod of Diamper E556828 entity
Predicate jurisdiction P82 FINISHED
Object Archdiocese of Angamaly NE NERFINISHED

How this triple was built (3 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 Angamaly | Statement: [Synod of Diamper, jurisdiction, Archdiocese of Angamaly]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Archdiocese of Angamaly
Context triple: [Synod of Diamper, jurisdiction, Archdiocese of Angamaly]
  • A. Diocese of Cochin
    The Diocese of Cochin is a historic Latin Catholic ecclesiastical jurisdiction in India, notable as one of the oldest dioceses established by the Portuguese in Asia.
  • B. Syro-Malabar Catholic Eparchy of Kottayam
    The Syro-Malabar Catholic Eparchy of Kottayam is an Eastern Catholic diocese in Kerala, India, serving primarily the Knanaya Catholic community within the Syro-Malabar Church.
  • C. Archdiocese of Madras and Mylapore
    The Archdiocese of Madras and Mylapore is a prominent Latin Catholic ecclesiastical jurisdiction in Chennai, India, formed by the merger of historic Madras and Mylapore sees and serving as a major metropolitan center for the Church in the region.
  • D. Diocese of Mylapore
    The Diocese of Mylapore was a historic Roman Catholic jurisdiction based in present-day Chennai, India, known for its association with early Portuguese missions and the tomb of St. Thomas the Apostle.
  • E. Diocese of Vellore
    The Diocese of Vellore is a Christian ecclesiastical jurisdiction in India, centered in the city of Vellore and responsible for overseeing local parishes and church activities within its territory.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Archdiocese of Angamaly
Target entity description: The Archdiocese of Angamaly is a historic East Syriac Christian ecclesiastical jurisdiction in Kerala, India, long serving as a principal center of the Saint Thomas Christians.
  • A. Diocese of Cochin
    The Diocese of Cochin is a historic Latin Catholic ecclesiastical jurisdiction in India, notable as one of the oldest dioceses established by the Portuguese in Asia.
  • B. Syro-Malabar Catholic Eparchy of Kottayam
    The Syro-Malabar Catholic Eparchy of Kottayam is an Eastern Catholic diocese in Kerala, India, serving primarily the Knanaya Catholic community within the Syro-Malabar Church.
  • C. Archdiocese of Madras and Mylapore
    The Archdiocese of Madras and Mylapore is a prominent Latin Catholic ecclesiastical jurisdiction in Chennai, India, formed by the merger of historic Madras and Mylapore sees and serving as a major metropolitan center for the Church in the region.
  • D. Diocese of Mylapore
    The Diocese of Mylapore was a historic Roman Catholic jurisdiction based in present-day Chennai, India, known for its association with early Portuguese missions and the tomb of St. Thomas the Apostle.
  • E. Diocese of Vellore
    The Diocese of Vellore is a Christian ecclesiastical jurisdiction in India, centered in the city of Vellore and responsible for overseeing local parishes and church activities within its territory.
  • F. None of above. chosen

Provenance (2 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_69e11e5657e881909f16ca58352c50da completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15e338dfc819082e1eeede3805fb9 completed April 29, 2026, 1:26 a.m.
Created at: April 16, 2026, 8:50 p.m.