Triple

T36277685
Position Surface form Disambiguated ID Type / Status
Subject Catholic Church in India E892851 entity
Predicate hasLatinMetropolitanSee P200743 FINISHED
Object Archdiocese of Bombay 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: Archdiocese of Bombay | Statement: [Catholic Church in India, hasLatinMetropolitanSee, Archdiocese of Bombay]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLatinMetropolitanSee
Context triple: [Catholic Church in India, hasLatinMetropolitanSee, Archdiocese of Bombay]
  • A. isMetropolitanOf
    Indicates that one entity is the primary metropolitan area or major urban center associated with another entity, such as a region, country, or administrative division.
  • B. metropolitanOf
    Indicates that one place serves as the primary metropolitan center or core urban area for another place or region.
  • C. hasLatinHierarchyCenter
    Indicates that an entity has a central or primary position within a Latin-based hierarchical structure.
  • D. metropolitanAreaWith
    Indicates that one entity is a metropolitan area that includes, is associated with, or encompasses the other entity.
  • E. hasMetropolitanAreaName
    Indicates that an entity is associated with a metropolitan area identified by a specific name.
  • 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_69f76e488f34819083e254dbe288c27a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ffaa7bc45c8190b907db8579244a7b completed May 9, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69ffa9f6c9a481908fbd4d18b311cbe2 completed May 9, 2026, 9:41 p.m.
PDg Predicate description generation batch_69ffaa7af814819095ed51ea1989ff14 completed May 9, 2026, 9:43 p.m.
Created at: May 3, 2026, 4:09 p.m.