Triple

T1282572
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Gloucester E27358 entity
Predicate hasSynodicalGovernment P26716 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: [Diocese of Gloucester, hasSynodicalGovernment, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSynodicalGovernment
Context triple: [Diocese of Gloucester, hasSynodicalGovernment, yes]
  • A. hasSynod
    Indicates that an entity is associated with, governed by, or participates in a particular synod (a formal ecclesiastical council or assembly).
  • B. hasConsolidatedGovernmentWith
    Indicates that two or more previously separate governmental entities have been merged into a single, unified government structure.
  • C. hasPolity
    Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
  • D. hasApostolicSee
    Indicates that a religious jurisdiction or entity is under the authority or oversight of a particular apostolic see (central episcopal seat).
  • E. hasGovernmentBody
    Indicates that one entity serves as the official governing or administrative body responsible for overseeing or managing another entity.
  • 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_69a496d3710c8190955dee8bc0dacb50 completed March 1, 2026, 7:43 p.m.
NER Named-entity recognition batch_69a4c0b47be08190828a1c0a11d94ce8 completed March 1, 2026, 10:41 p.m.
PD Predicate disambiguation batch_69a4bee276d8819092f71c5a1140bb61 completed March 1, 2026, 10:34 p.m.
PDg Predicate description generation batch_69a4bf60545c8190901ccfb2cb7c4b41 completed March 1, 2026, 10:36 p.m.
Created at: March 1, 2026, 7:50 p.m.