Triple

T18648997
Position Surface form Disambiguated ID Type / Status
Subject Aquila of Sinope’s Greek translation E455882 entity
Predicate differenceFromSeptuagint P132880 FINISHED
Object more literal 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: more literal | Statement: [Aquila of Sinope’s Greek translation, differenceFromSeptuagint, more literal]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: differenceFromSeptuagint
Context triple: [Aquila of Sinope’s Greek translation, differenceFromSeptuagint, more literal]
  • A. isBiblicalVariantOf
    Indicates that one textual form or reading is a variant version of another within the biblical textual tradition.
  • B. numberingInSeptuagintVulgate
    Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
  • C. textualBasisNewTestament
    Indicates that something is based on, derived from, or justified by a text from the New Testament.
  • D. usedScriptureTranslation
    Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
  • E. usesOldTestamentExamplesFrom
    Indicates that one entity draws on or cites examples from the Old Testament that originate from another entity.
  • 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_69d8d38ea1e88190997e9b231190ba6f completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e5500fd7cc819095c5e742013b8d75 completed April 19, 2026, 9:58 p.m.
PD Predicate disambiguation batch_69e478d85864819093cbad5ed9b54878 completed April 19, 2026, 6:40 a.m.
PDg Predicate description generation batch_69e484121cd48190bf583b4c94636a30 completed April 19, 2026, 7:28 a.m.
Created at: April 10, 2026, 11:47 a.m.