Triple

T7002021
Position Surface form Disambiguated ID Type / Status
Subject Jesuit Church Lucerne E162357 entity
Predicate hasConfessionals P73525 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: [Jesuit Church Lucerne, hasConfessionals, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasConfessionals
Context triple: [Jesuit Church Lucerne, hasConfessionals, yes]
  • A. hasConfessionalDocument
    Indicates that an entity possesses, is associated with, or is documented by a formal confessional document (such as a statement of faith, creed, or confession).
  • B. usesConfessions
    Indicates that one entity employs or relies on another entity’s confessions as a basis for some action, decision, or outcome.
  • C. usesConfession
    Indicates that one entity employs or relies on a confession (typically an admission of guilt or wrongdoing) as part of its actions or reasoning toward another entity or outcome.
  • D. madePublicConfessionAt
    Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
  • E. associatedConfession
    Indicates a relationship where one entity is linked to a specific confession, admission, or statement acknowledging guilt or responsibility.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc1115c48190a9363473ae21b6c1 completed March 27, 2026, 7:35 p.m.
PD Predicate disambiguation batch_69c6d7c67c94819084fdcf0398606027 completed March 27, 2026, 7:17 p.m.
PDg Predicate description generation batch_69c6d8c575f081908b43d95d1d99b1a4 completed March 27, 2026, 7:21 p.m.
Created at: March 27, 2026, 2:33 p.m.