Triple

T10992688
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic dioceses E259787 entity
Predicate hasKeyOfficer P4012 FINISHED
Object vicar general 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: vicar general | Statement: [Roman Catholic dioceses, hasKeyOfficer, vicar general]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKeyOfficer
Context triple: [Roman Catholic dioceses, hasKeyOfficer, vicar general]
  • A. isOfficerOf chosen
    Indicates that one entity holds an official position, role, or office within another entity (such as an organization, group, or institution).
  • B. hasJudicialOfficer
    Indicates that an entity is associated with or served by a specific judicial officer (such as a judge or magistrate) responsible for legal or court-related functions.
  • C. hasKeyAgency
    Indicates that an entity serves as the primary responsible or controlling agency for another entity, action, or process.
  • D. hasKeyOrganization
    Indicates that an entity is associated with or primarily represented by a main or primary organization.
  • E. hasOfficeHolderType
    Indicates that an office or position is associated with a specific type or category of office holder (e.g., elected official, appointed official).
  • F. None of above.

Provenance (3 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_69d6aa8a6a548190a750f944ccdc8064 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d795d32f9081909def643571499521 completed April 9, 2026, 12:04 p.m.
PD Predicate disambiguation batch_69d72e93ac648190b46c5d12bf3eb1e9 completed April 9, 2026, 4:44 a.m.
Created at: April 8, 2026, 9:24 p.m.