Triple

T37461029
Position Surface form Disambiguated ID Type / Status
Subject Y’Shaarj, Rage Unbound E930915 entity
Predicate voiceoverLanguage P181798 FINISHED
Object Localized per client language 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: Localized per client language | Statement: [Y’Shaarj, Rage Unbound, voiceoverLanguage, Localized per client language]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: voiceoverLanguage
Context triple: [Y’Shaarj, Rage Unbound, voiceoverLanguage, Localized per client language]
  • A. voiceActingLanguage
    Indicates the language in which a voice acting performance is delivered.
  • B. voiceRecordingLanguage chosen
    Indicates the language in which a voice recording is spoken or produced.
  • C. languageSpokenOnScreen
    Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
  • D. voiceInUSDub
    Indicates that an entity provides the voice performance for a character or role in the United States (U.S.) dubbed version of a work.
  • E. languageOfVocalization
    Indicates the language in which a vocalization (such as speech or singing) is produced.
  • 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_69f76ec1a1148190b0a961f188d621b0 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcda3699948190adb57625bae08091 completed May 7, 2026, 6:30 p.m.
PD Predicate disambiguation batch_69fcd8fd16d08190b0aca6e19a632e99 completed May 7, 2026, 6:25 p.m.
Created at: May 3, 2026, 4:17 p.m.