Triple

T37546500
Position Surface form Disambiguated ID Type / Status
Subject Apologia Pro Vita Sua E933477 entity
Predicate defendsConversionTo P191058 FINISHED
Object Roman Catholic Church NE NERFINISHED

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: Roman Catholic Church | Statement: [Apologia Pro Vita Sua, defendsConversionTo, Roman Catholic Church]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: defendsConversionTo
Context triple: [Apologia Pro Vita Sua, defendsConversionTo, Roman Catholic Church]
  • A. defendsConversionOf chosen
    Indicates that one entity actively supports or justifies the act of converting another entity from one state, form, or condition to another.
  • B. allowsConversionTo
    Indicates that one entity permits or enables transformation or change into another specified form or state.
  • C. isConversion
    Indicates that one entity is transformed or converted into another, typically changing its form, type, or representation.
  • D. isForcedToConvertTo
    Indicates that one entity is compelled, against its will, to change its beliefs, affiliation, or status to match that of another entity.
  • E. opposedConversionOf
    Indicates that one entity actively resisted, objected to, or worked against the process of converting or changing 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_69f76eca55bc8190acf25741793d5dac completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:17 p.m.