Triple

T5025355
Position Surface form Disambiguated ID Type / Status
Subject Holy Synod of Bishops E112960 entity
Predicate canDefine P31625 FINISHED
Object positions on doctrinal and moral issues 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: positions on doctrinal and moral issues | Statement: [Holy Synod of Bishops, canDefine, positions on doctrinal and moral issues]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canDefine
Context triple: [Holy Synod of Bishops, canDefine, positions on doctrinal and moral issues]
  • A. canDeclare
    Indicates that one entity has the authority or ability to formally declare or announce something about another entity or situation.
  • B. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
  • C. canMake
    Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
  • D. canDetermine chosen
    Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
  • E. canOwn
    Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd736a0f8c819091d06275954329e9 completed March 20, 2026, 4:18 p.m.
PD Predicate disambiguation batch_69bd71509e9c8190a60c1d8d04936a12 completed March 20, 2026, 4:09 p.m.
Created at: March 20, 2026, 1:36 p.m.