Triple

T3875146
Position Surface form Disambiguated ID Type / Status
Subject Personal Prelature of Ayaviri E92482 entity
Predicate underPastoralCareOf P28603 FINISHED
Object prelate of Ayaviri 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: prelate of Ayaviri | Statement: [Personal Prelature of Ayaviri, underPastoralCareOf, prelate of Ayaviri]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: underPastoralCareOf
Context triple: [Personal Prelature of Ayaviri, underPastoralCareOf, prelate of Ayaviri]
  • A. hasPastoralCenter
    Indicates that an entity possesses or is associated with a pastoral center as one of its facilities or organizational components.
  • B. underAuspicesOf
    Indicates that an action, event, or entity operates under the sponsorship, authority, or guidance of another party.
  • C. adoptedUnder
    Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
  • D. tookCareOf chosen
    Indicates that one entity provided care, support, or maintenance for another entity over a period of time.
  • E. adopts
    Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
  • 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_69aed967448c819086c4b358d37b25aa completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aef1515c688190a38332aedeed8a76 completed March 9, 2026, 4:12 p.m.
PD Predicate disambiguation batch_69aee7574c408190893e70bf80514838 completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:20 p.m.