Triple

T26823286
Position Surface form Disambiguated ID Type / Status
Subject Part I: The Pentateuch E675309 entity
Predicate scripturalCanonCovered P33314 FINISHED
Object Torah NE NERFINISHED

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: Torah | Statement: [Part I: The Pentateuch, scripturalCanonCovered, Torah]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scripturalCanonCovered
Context triple: [Part I: The Pentateuch, scripturalCanonCovered, Torah]
  • A. scripturalCanonStatus
    Indicates whether and how a text is recognized as part of an authoritative scriptural canon within a given religious or doctrinal tradition.
  • B. scripturalCorpusAnalyzed
    Indicates that a particular scriptural corpus has been examined or studied, typically in a systematic or scholarly manner.
  • C. scripturePolicy
    Indicates a rule, guideline, or stance governing how scripture is treated, used, interpreted, or managed.
  • D. canonizedScriptureIn chosen
    Indicates that a text or scripture has been formally recognized and included as canonical within a particular religious tradition, community, or collection.
  • E. scripturalCorpus
    Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, 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_69eee9b6b28481909332f83eb17e5170 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f6562fd3488190be1acd8c526a28d2 completed May 2, 2026, 7:53 p.m.
PD Predicate disambiguation batch_69f651a731508190bb0c8c2462eba224 completed May 2, 2026, 7:33 p.m.
Created at: April 27, 2026, 4:56 a.m.