Triple

T4759436
Position Surface form Disambiguated ID Type / Status
Subject Targums E105664 entity
Predicate relatedConcept P37 FINISHED
Object Peshitta E46025 NE 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: Peshitta | Statement: [Targums, relatedConcept, Peshitta]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Peshitta
Context triple: [Targums, relatedConcept, Peshitta]
  • A. Peshitta chosen
    The Peshitta is the standard Syriac version of the Bible, historically central to Syriac Christianity’s scripture and liturgy.
  • B. Septuagint
    The Septuagint is an ancient Greek translation of the Hebrew Scriptures that became the primary Old Testament text for early Christians and Greek-speaking Jews.
  • C. Textus Receptus
    Textus Receptus is a traditional printed Greek New Testament text compiled in the 16th century that became the primary basis for many early Protestant Bible translations.
  • D. Codex Sinaiticus
    Codex Sinaiticus is one of the oldest and most complete surviving manuscripts of the Christian Bible, written in Greek on parchment in the 4th century.
  • E. Codex Bezae
    Codex Bezae is a 5th-century Greek-Latin bilingual manuscript of the New Testament, notable for its distinctive textual variants and importance in biblical textual criticism.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69bd43f14cac819081c7c69803648211 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd650c11f4819098cd1f490f711dc8 completed March 20, 2026, 3:17 p.m.
NED1 Entity disambiguation (via context triple) batch_69be3a77eb848190877eb5e15c7e6b0c completed March 21, 2026, 6:28 a.m.
Created at: March 20, 2026, 1:20 p.m.