Triple

T4586565
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Willesden E103380 entity
Predicate confirmationRole P18494 FINISHED
Object confirms lay people 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: confirms lay people | Statement: [Bishop of Willesden, confirmationRole, confirms lay people]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: confirmationRole
Context triple: [Bishop of Willesden, confirmationRole, confirms lay people]
  • A. confirmedBy
    Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
  • B. confirmationMethod
    Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
  • C. confirmationOutcome
    Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
  • D. confirmedFor
    Indicates that an entity has been officially approved, scheduled, or validated to participate in, receive, or be associated with another specified entity or event.
  • E. confirmationPower chosen
    Indicates that one entity has the authority or capacity to approve, validate, or formally confirm the actions, decisions, or status of 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_69bd43dccaf08190aa89e9991a289719 completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5906a43c81908fb11bf8f94be122 completed March 20, 2026, 2:26 p.m.
PD Predicate disambiguation batch_69bd522acbcc8190bf24d9517793a2c1 completed March 20, 2026, 1:56 p.m.
Created at: March 20, 2026, 1:10 p.m.