Triple

T35734697
Position Surface form Disambiguated ID Type / Status
Subject Roman Catholic Diocese of Fargo E1032854 entity
Predicate hasPastoralMinistries P195352 FINISHED
Object youth ministry 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: youth ministry | Statement: [Roman Catholic Diocese of Fargo, hasPastoralMinistries, youth ministry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPastoralMinistries
Context triple: [Roman Catholic Diocese of Fargo, hasPastoralMinistries, youth ministry]
  • A. hasPastoralMission
    Indicates that an entity is responsible for providing spiritual care, guidance, or religious leadership to a community or group.
  • B. hasPastoralPrograms chosen
    Indicates that an entity offers or conducts pastoral care or ministry programs.
  • C. hasPastoralCareFocus
    Indicates that the subject is oriented toward providing spiritual, emotional, or pastoral support and guidance to others.
  • D. hasLayMinistry
    Indicates that an entity participates in or is associated with a lay (non-ordained) ministry role or service within a religious context.
  • E. hasPastoralCareSystem
    Indicates that an entity has an organized system or framework in place to provide pastoral or personal care and support to individuals.
  • 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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ffe12ee59c8190bc7da386e6d5332d completed May 10, 2026, 1:36 a.m.
PD Predicate disambiguation batch_69ffe0a138bc8190a3d4b48cd579e985 completed May 10, 2026, 1:34 a.m.
Created at: May 3, 2026, 4:05 p.m.