Triple

T19979594
Position Surface form Disambiguated ID Type / Status
Subject Regularis Concordia E493779 entity
Predicate typeOfNormativity P2826 FINISHED
Object liturgical norm 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: liturgical norm | Statement: [Regularis Concordia, typeOfNormativity, liturgical norm]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfNormativity
Context triple: [Regularis Concordia, typeOfNormativity, liturgical norm]
  • A. normativeFor
    Indicates that something establishes, prescribes, or encodes the norms, standards, or rules that should govern another thing’s behavior or state.
  • B. natureOfRule
    Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
  • C. levelOfNorm
    Indicates the degree or extent to which something conforms to a specified norm, standard, or expected behavior.
  • D. hasNormativeCategory
    Indicates that something is associated with a particular normative category, such as a standard, rule, or evaluative classification that prescribes how it ought to be regarded or treated.
  • E. normType chosen
    Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
  • 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_69da626a67648190af9653832a3aeced completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e65d11d2108190bd1d91fdc834888b completed April 20, 2026, 5:06 p.m.
PD Predicate disambiguation batch_69e537fae79c81909eae39500766d0b6 completed April 19, 2026, 8:15 p.m.
Created at: April 11, 2026, 3:27 p.m.