Triple

T15043980
Position Surface form Disambiguated ID Type / Status
Subject An Answer to a Certain Libel Intituled An Admonition to the Parliament E379174 entity
Predicate instanceOf P0 FINISHED
Object religious controversy literature C16317 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: religious controversy literature
Context triple: [An Answer to a Certain Libel Intituled An Admonition to the Parliament, instanceOf, religious controversy literature]
  • A. religious controversy
    Religious controversy is a sustained conflict or debate arising from differing beliefs, doctrines, practices, or interpretations within or between religious traditions.
  • B. religious literature
    Religious literature is a body of written works—such as scriptures, theological treatises, devotional texts, and spiritual narratives—created to express, interpret, and transmit the beliefs, practices, values, and experiences of a religious tradition.
  • C. religious discourse collection
    A religious discourse collection is an organized set of spoken, written, or multimedia texts that document, analyze, or present religious beliefs, practices, and debates across contexts and traditions.
  • D. controversial religion
    A controversial religion is a belief system whose doctrines, practices, or social impact provoke significant public debate, criticism, or conflict within or across societies.
  • E. Christian polemical work chosen
    A Christian polemical work is a text written from a Christian perspective that argues against, critiques, or refutes opposing religious, philosophical, or ideological positions to defend or promote Christian doctrine.
  • F. None of above.

Provenance (1 batch)

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_69d85cd64d108190853797a95c11cc45 completed April 10, 2026, 2:13 a.m.
Created at: April 10, 2026, 3 a.m.