Triple

T16064036
Position Surface form Disambiguated ID Type / Status
Subject Reformed Baptist movement E389687 entity
Predicate hasViewOnCovenants P30449 FINISHED
Object distinction between old and new covenants 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: distinction between old and new covenants | Statement: [Reformed Baptist movement, hasViewOnCovenants, distinction between old and new covenants]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasViewOnCovenants
Context triple: [Reformed Baptist movement, hasViewOnCovenants, distinction between old and new covenants]
  • A. hasCovenants
    Indicates that one entity is bound by or associated with formal covenants, agreements, or binding promises in relation to another entity or context.
  • B. covenantView chosen
    Indicates a relationship where one party observes, understands, or interprets the terms, conditions, or implications of a covenant or binding agreement.
  • C. covenantAssociation
    Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
  • D. covenantStatus
    Indicates the current state or condition of a covenant or binding agreement between parties.
  • E. covenantWith
    Indicates a formal, binding agreement or promise established between two or more parties.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1858a00888190b8505071575dc56f completed April 17, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e18272f2288190a17d45fb01cc2b07 completed April 17, 2026, 12:44 a.m.
Created at: April 10, 2026, 4:57 a.m.