Triple

T32964889
Position Surface form Disambiguated ID Type / Status
Subject Kirchliche Synode E843341 entity
Predicate hasDecisionProcess P198147 FINISHED
Object Mehrheitsbeschluss 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: Mehrheitsbeschluss | Statement: [Kirchliche Synode, hasDecisionProcess, Mehrheitsbeschluss]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDecisionProcess
Context triple: [Kirchliche Synode, hasDecisionProcess, Mehrheitsbeschluss]
  • A. hasDecisionPoint
    Indicates that there is a specific moment or juncture at which a choice between alternative options or paths must be made.
  • B. hasDecisionForm
    Indicates that an entity is associated with, or represented by, a particular decision document or formal decision record.
  • C. hasFinalDecisionOn
    Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
  • D. hasDecisionProcedure
    Indicates that there exists a systematic, effective method for determining, for any given input, whether the predicate or problem in question holds or has a solution.
  • E. hasDecisionMaker
    Indicates that one entity serves as the decision-making authority or agent for another entity.
  • F. None of above. chosen

Provenance (4 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_69f3494af2808190ad98cec2f1bc0fe6 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fecd0a732c819097bdd3eb69b6158c completed May 9, 2026, 5:58 a.m.
PD Predicate disambiguation batch_69fecc0318d481908b5b20598a76a9fe completed May 9, 2026, 5:54 a.m.
PDg Predicate description generation batch_69fecd091abc8190872974de731a80fa completed May 9, 2026, 5:58 a.m.
Created at: May 1, 2026, 1:21 a.m.