Triple

T350746
Position Surface form Disambiguated ID Type / Status
Subject Protestant Christianity E7436 entity
Predicate usesScripturalCanon P5605 FINISHED
Object Protestant Old Testament canon 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: Protestant Old Testament canon | Statement: [Protestant Christianity, usesScripturalCanon, Protestant Old Testament canon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesScripturalCanon
Context triple: [Protestant Christianity, usesScripturalCanon, Protestant Old Testament canon]
  • A. hasScripture chosen
    Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
  • B. scripturalBasis
    Indicates that one entity serves as the religious or scriptural foundation, support, or justification for another entity (such as a belief, practice, or doctrine).
  • C. hasViewOnScripture
    Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
  • D. hasLanguageOfScripture
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • E. scriptureType
    Indicates the classification or category of a scripture in relation to its type or genre.
  • 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_69a2e7e696948190bebc966535995e45 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2eb1f028c819098fa6480b4ca5cf0 completed Feb. 28, 2026, 1:18 p.m.
PD Predicate disambiguation batch_69a2e955d1f88190bd687c46fa7c5469 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.