Triple

T36869128
Position Surface form Disambiguated ID Type / Status
Subject Russian Orthodox Old-Rite Church E911176 entity
Predicate regardsNikonianReformsAs P131226 FINISHED
Object unwarranted innovations 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: unwarranted innovations | Statement: [Russian Orthodox Old-Rite Church, regardsNikonianReformsAs, unwarranted innovations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regardsNikonianReformsAs
Context triple: [Russian Orthodox Old-Rite Church, regardsNikonianReformsAs, unwarranted innovations]
  • A. viewsReformsAs chosen
    Indicates that one entity regards or interprets certain reforms in a particular way (e.g., as positive, negative, necessary, or harmful).
  • B. reformsBy
    Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
  • C. subjectToReformBy
    Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
  • D. relatedReforms
    Indicates that one reform is connected or associated with another reform, typically through shared goals, content, or impact.
  • E. associatedReforms
    Indicates a relationship where certain reforms are linked or connected to a given entity, such as a policy, event, or individual.
  • 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_69f76e80f6f0819091cba8e19b269615 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f9fd6834cc8190aa27153d6a99f3bb completed May 5, 2026, 2:23 p.m.
PD Predicate disambiguation batch_69f7cf7890008190a8bc355ff2d61c86 completed May 3, 2026, 10:43 p.m.
Created at: May 3, 2026, 4:13 p.m.