Triple

T33034083
Position Surface form Disambiguated ID Type / Status
Subject Evangelical Lutheran Church in Bosnia and Herzegovina E845254 entity
Predicate hasClericalCollarTradition P42772 FINISHED
Object Yes 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: Yes | Statement: [Evangelical Lutheran Church in Bosnia and Herzegovina, hasClericalCollarTradition, Yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasClericalCollarTradition
Context triple: [Evangelical Lutheran Church in Bosnia and Herzegovina, hasClericalCollarTradition, Yes]
  • A. hasClericalVestments chosen
    Indicates that one entity possesses or is associated with the clerical vestments (religious garments) of another entity.
  • B. hasClericalAssociation
    Indicates a relationship in which an entity is connected to or involved with clerical roles, duties, or religious office.
  • C. hasClericalDiscipline
    Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
  • D. hasClergyType
    Indicates the specific category or role of clergy associated with an entity.
  • E. hasClericalFunction
    Indicates that an entity performs, is responsible for, or is associated with a clerical or administrative function.
  • 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_69f34951348c8190b56746b0a7018182 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd35d108908190b79b1e8e6bbd62aa completed May 8, 2026, 1:01 a.m.
PD Predicate disambiguation batch_69fd34cb46108190b43c3b7f67ec4cd4 completed May 8, 2026, 12:56 a.m.
Created at: May 1, 2026, 1:24 a.m.