Triple

T3258831
Position Surface form Disambiguated ID Type / Status
Subject Berom language E68361 entity
Predicate hasBiblePortionsTranslated P46921 FINISHED
Object yes 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: yes | Statement: [Berom language, hasBiblePortionsTranslated, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBiblePortionsTranslated
Context triple: [Berom language, hasBiblePortionsTranslated, yes]
  • A. scriptureTranslatedBy
    Indicates that a particular scripture has been translated by a specific agent (such as a person, group, or organization).
  • B. scriptureTypeTranslated
    Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
  • C. usedScriptureTranslation
    Indicates that one entity employed or relied on a particular translation of scripture in its actions, works, or communications.
  • D. hasLanguageOfScripture
    Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
  • E. hasWorkTranslatedInto
    Indicates that a work has been translated into a specified language or target work.
  • 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_69ad858f74408190bcbd07f967cd7bd0 completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adafa4f40c81909adfd0f7f568e3ce completed March 8, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69ada41ae74081909a0d1d696be8e35e completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada525bb2c8190b773efe6d696b6ab completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:09 p.m.