Triple

T18304607
Position Surface form Disambiguated ID Type / Status
Subject Rages E438449 entity
Predicate usedIn P98 FINISHED
Object Vulgate 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: Vulgate | Statement: [Rages, usedIn, Vulgate]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vulgate
Context triple: [Rages, usedIn, Vulgate]
  • A. Vulgate chosen
    The Vulgate is the late-4th-century Latin version of the Bible, traditionally attributed to St. Jerome, that became the Catholic Church’s standard biblical text for many centuries.
  • B. Douay–Rheims Bible
    The Douay–Rheims Bible is an early English translation of the Latin Vulgate produced by English Catholics in exile during the late 16th and early 17th centuries.
  • C. Peshitta
    The Peshitta is the standard Syriac version of the Bible, historically central to Syriac Christianity’s scripture and liturgy.
  • D. 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.
  • E. 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.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5018256508190b024980e3a4a3ae9 completed April 19, 2026, 4:23 p.m.
Created at: April 10, 2026, 10:35 a.m.