Triple

T48056
Position Surface form Disambiguated ID Type / Status
Subject ECUSA E943 entity
Predicate scriptureStatus P2324 FINISHED
Object scripture as primary source of authority 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: scripture as primary source of authority | Statement: [ECUSA, scriptureStatus, scripture as primary source of authority]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scriptureStatus
Context triple: [ECUSA, scriptureStatus, scripture as primary source of authority]
  • A. hasViewOnScripture chosen
    Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
  • 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. hasLanguageOfScripture
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • D. sharesScriptureWith
    Indicates that one entity communicates or distributes religious or scriptural texts to another entity.
  • E. statusInChristianity
    Indicates the recognized role, standing, or significance that something or someone holds within Christian belief, practice, or tradition.
  • 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_69a2480baefc81909951b14058479aa2 completed Feb. 28, 2026, 1:42 a.m.
NER Named-entity recognition batch_69a24c1a5c14819088748317a3f262c8 completed Feb. 28, 2026, 1:59 a.m.
PD Predicate disambiguation batch_69a24abe7cb481908d969e54032f6c75 completed Feb. 28, 2026, 1:54 a.m.
Created at: Feb. 28, 2026, 1:47 a.m.