Triple

T6146060
Position Surface form Disambiguated ID Type / Status
Subject Anglican Diocese of Melbourne E137078 entity
Predicate isMetropolitanDiocese P69438 FINISHED
Object true 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: true | Statement: [Anglican Diocese of Melbourne, isMetropolitanDiocese, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMetropolitanDiocese
Context triple: [Anglican Diocese of Melbourne, isMetropolitanDiocese, true]
  • A. hasMetropolitanArchdiocese
    Indicates that an ecclesiastical jurisdiction is under the authority or oversight of a specified metropolitan archdiocese.
  • B. isMetropolitanChurch
    Indicates that a church holds metropolitan status, serving as the principal ecclesiastical authority over other churches within a defined region or province.
  • C. isDiocesanSeatOf
    Indicates that a location serves as the central administrative seat or headquarters of a particular diocese.
  • D. metropolitanArchdioceseOf
    Indicates that one ecclesiastical jurisdiction is the metropolitan archdiocese that has authority over another church territory or diocese.
  • E. hasMetropolitanBishop
    Indicates that a given ecclesiastical jurisdiction is under the authority or oversight of a specific metropolitan bishop.
  • F. None of above. chosen

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_69c008a2c6308190a56519b22d55d083 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05cdd2dc0819080a4adf0cead3603 completed March 22, 2026, 9:19 p.m.
PD Predicate disambiguation batch_69c055f39e0881909ae56444b1b48929 completed March 22, 2026, 8:49 p.m.
PDg Predicate description generation batch_69c056c87340819088003f427706ebf8 completed March 22, 2026, 8:53 p.m.
Created at: March 22, 2026, 4:16 p.m.