Triple

T2398163
Position Surface form Disambiguated ID Type / Status
Subject Sadducees E47698 entity
Predicate positionOnOralLaw P9295 FINISHED
Object rejected Pharisaic oral tradition 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: rejected Pharisaic oral tradition | Statement: [Sadducees, positionOnOralLaw, rejected Pharisaic oral tradition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionOnOralLaw
Context triple: [Sadducees, positionOnOralLaw, rejected Pharisaic oral tradition]
  • A. positionInTanakh
    Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
  • B. positionInHebrewBible
    Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
  • C. positionOnLaw chosen
    Indicates a stance, opinion, or interpretation that an entity holds regarding a specific law or legal provision.
  • D. halakhicSource
    Indicates a relationship where one item serves as the halakhic (Jewish legal) basis, authority, or source text for another.
  • E. positionInBible
    Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
  • 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_69a88a1c450c81909f61abb8b6863885 completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abc8c5f0948190b4ea729693d8c306 completed March 7, 2026, 6:42 a.m.
PD Predicate disambiguation batch_69abc5a3825c81909ec6111dfc165453 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:57 p.m.