Triple

T38268799
Position Surface form Disambiguated ID Type / Status
Subject Syro-Malankara Catholic exarchates E1021144 entity
Predicate haveTerritorialJurisdiction P190230 FINISHED
Object yes 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: yes | Statement: [Syro-Malankara Catholic exarchates, haveTerritorialJurisdiction, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: haveTerritorialJurisdiction
Context triple: [Syro-Malankara Catholic exarchates, haveTerritorialJurisdiction, yes]
  • A. territorialJurisdictionIncludes
    Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
  • B. hasJurisdictionOver
    Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
  • C. territorialJurisdictionOf
    Indicates that one entity has legal or administrative authority over a specific geographic area or territory associated with another entity.
  • D. hasPoliticalJurisdictionType
    Indicates the type or category of political jurisdiction that applies to or governs an entity.
  • E. hasJurisidiction
    Indicates that one entity holds legal authority or control over another entity, area, or matter.
  • 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_69f76dee198c8190bf5109421e47a658 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcc3321ef081908023590ba70ba0cf completed May 7, 2026, 4:52 p.m.
PD Predicate disambiguation batch_69fcb0fdc6e08190b05e894c59481a0d completed May 7, 2026, 3:34 p.m.
PDg Predicate description generation batch_69fcc330b4288190858b49d986160706 completed May 7, 2026, 4:52 p.m.
Created at: May 3, 2026, 4:30 p.m.