Triple

T21531493
Position Surface form Disambiguated ID Type / Status
Subject Our Lady of Divine Providence E531240 entity
Predicate roleAscribed P108327 FINISHED
Object protector of the faithful 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: protector of the faithful | Statement: [Our Lady of Divine Providence, roleAscribed, protector of the faithful]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleAscribed
Context triple: [Our Lady of Divine Providence, roleAscribed, protector of the faithful]
  • A. roleAccordingTo
    Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
  • B. role
    Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
  • C. roleInName
    Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
  • D. perceivedRole chosen
    Indicates the role or function that one entity is regarded or interpreted as having in relation to another, based on perception rather than objective status.
  • E. representedRole
    Indicates that one entity serves as a stand-in, proxy, or representative performing a role on behalf of another entity.
  • 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_69e0c45e5b8881908ac18fc2f493b114 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee9d08ebf881909574e098404f93fa completed April 26, 2026, 11:17 p.m.
PD Predicate disambiguation batch_69e6320043bc81909417c41a718652ba completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:27 p.m.