Triple

T207578
Position Surface form Disambiguated ID Type / Status
Subject New International Version E4641 entity
Predicate translationApproach P5473 FINISHED
Object dynamic equivalence 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: dynamic equivalence | Statement: [New International Version, translationApproach, dynamic equivalence]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: translationApproach
Context triple: [New International Version, translationApproach, dynamic equivalence]
  • A. translationMethod
    Indicates the technique or process used to translate content from one language or form to another.
  • B. translator
    Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
  • C. alternativeTransliteration
    Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
  • D. translationPhilosophy chosen
    Indicates the guiding approach or set of principles that governs how a text is translated from one language to another.
  • E. languageShift
    Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
  • 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_69a25737567c81908f9c505300239181 completed Feb. 28, 2026, 2:47 a.m.
NER Named-entity recognition batch_69a25e2aba74819093eddd8d820260c0 completed Feb. 28, 2026, 3:16 a.m.
PD Predicate disambiguation batch_69a25b4c7f908190876c1041db52dffc completed Feb. 28, 2026, 3:04 a.m.
Created at: Feb. 28, 2026, 2:51 a.m.