Triple

T4768273
Position Surface form Disambiguated ID Type / Status
Subject Huldah E105863 entity
Predicate reasonForJudgment P59235 FINISHED
Object Judah burned incense to other gods 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: Judah burned incense to other gods | Statement: [Huldah, reasonForJudgment, Judah burned incense to other gods]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForJudgment
Context triple: [Huldah, reasonForJudgment, Judah burned incense to other gods]
  • A. statedReason
    Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
  • B. reasonForAppealDecision
    Indicates the justification or grounds cited for making a particular appeal decision.
  • C. reasonForConviction
    Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
  • D. reasonForDismissal
    Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
  • E. rejectedJustification
    Indicates that a proposed justification or reason offered in a context (e.g., argument, decision, or claim) has been evaluated and not accepted as valid or sufficient.
  • F. None of above. chosen

Provenance (4 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd686ef1b08190ad60375592c9d6c0 completed March 20, 2026, 3:31 p.m.
PD Predicate disambiguation batch_69bd622807f881908e4bcb14f7731bac completed March 20, 2026, 3:05 p.m.
PDg Predicate description generation batch_69bd686dc7b88190b41e8a362701080d completed March 20, 2026, 3:31 p.m.
Created at: March 20, 2026, 1:21 p.m.