Triple

T453654
Position Surface form Disambiguated ID Type / Status
Subject Lambeth Conference E7184 entity
Predicate reasonForInception P6484 FINISHED
Object controversy over Bishop John William Colenso of Natal 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: controversy over Bishop John William Colenso of Natal | Statement: [Lambeth Conference, reasonForInception, controversy over Bishop John William Colenso of Natal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForInception
Context triple: [Lambeth Conference, reasonForInception, controversy over Bishop John William Colenso of Natal]
  • A. reasonForCreation
    Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
  • B. originalReason chosen
    Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
  • C. reasonWritten
    Indicates that one entity is the reason or motivation for which another entity was written or authored.
  • D. reasonForChange
    Indicates that one entity serves as the cause, justification, or motivation for a modification or change in another entity or state.
  • E. reasonForName
    Indicates the explanation or cause behind why an entity has a particular name.
  • 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_69a2e7e4676c81909ea0dbdecac0687c completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ef866e848190a5b700250ec56256 completed Feb. 28, 2026, 1:37 p.m.
PD Predicate disambiguation batch_69a2ede4de008190b5a6c159e741522e completed Feb. 28, 2026, 1:30 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.