Triple

T80665
Position Surface form Disambiguated ID Type / Status
Subject On the Origin of Species E1619 entity
Predicate controversialIn P1783 FINISHED
Object religious communities 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: religious communities | Statement: [On the Origin of Species, controversialIn, religious communities]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: controversialIn
Context triple: [On the Origin of Species, controversialIn, religious communities]
  • A. controversy chosen
    Indicates a situation in which there is active disagreement, dispute, or public debate between parties over a particular issue, action, or claim.
  • B. contestedBy
    Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
  • C. conflictIn
    Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
  • D. issue
    Indicates that an entity formally publishes, releases, or distributes something, such as a document, statement, or item, often in an official or authoritative capacity.
  • E. opposedBy
    Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position 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_69a24c60d19c8190a1b6c105ca59ef5b completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a25053ca208190a371b0d38000c2b9 completed Feb. 28, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69a24eb2998c819082681da74601d446 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.