Triple

T2365012
Position Surface form Disambiguated ID Type / Status
Subject Roman Ritual E47359 entity
Predicate hasCanonicalRole P5454 FINISHED
Object normative source for many sacramental rites 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: normative source for many sacramental rites | Statement: [Roman Ritual, hasCanonicalRole, normative source for many sacramental rites]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCanonicalRole
Context triple: [Roman Ritual, hasCanonicalRole, normative source for many sacramental rites]
  • A. hasRole
    Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
  • B. hasCanonicalReference chosen
    Indicates that one entity serves as the authoritative or standard reference source for another entity.
  • C. hasRelativeRole
    Indicates that one entity holds a familial or kinship-based role in relation to another entity.
  • D. hasCanonicalPosition
    Indicates that an entity occupies a standard, officially recognized, or authoritative position or location within a defined structure or system.
  • E. hasEquivalentRole
    Indicates that two entities hold roles that are functionally the same or interchangeable in a given context.
  • 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_69a88a1a4a6081908645b0f2914521ab completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc7486cb48190acef1891cc87bdb1 completed March 7, 2026, 6:35 a.m.
PD Predicate disambiguation batch_69abc599b92c819093d9e15d4437705d completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:55 p.m.