Triple

T33370441
Position Surface form Disambiguated ID Type / Status
Subject Khazâd E854471 entity
Predicate usedInBattleCry P189395 FINISHED
Object Baruk Khazâd! Khazâd ai-mênu! 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: Baruk Khazâd! Khazâd ai-mênu! | Statement: [Khazâd, usedInBattleCry, Baruk Khazâd! Khazâd ai-mênu!]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInBattleCry
Context triple: [Khazâd, usedInBattleCry, Baruk Khazâd! Khazâd ai-mênu!]
  • A. battlecry
    Indicates a relationship where an entity utters or uses a shouted phrase or chant to inspire, rally, or signal others, typically in preparation for or during conflict.
  • B. battlecryText chosen
    Indicates the characteristic phrase or shout used as a battle cry during a conflict or confrontation.
  • C. battlecryChoice
    Indicates the specific battle cry that an entity selects or uses, typically as a vocal expression before or during combat.
  • D. hasBattlecry
    Indicates that an entity possesses or is associated with a specific battlecry, typically a shouted phrase or sound used at the onset of combat or action.
  • E. warCry
    Indicates a relationship where an entity utters or performs a loud, rallying shout or chant intended to inspire allies or intimidate opponents, typically in a conflict or competitive 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_69f3496bda8c8190bfc8fade9d1b791c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fe610e1f6881908f10070ba64643cf completed May 8, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69fe604c6c008190ad659e9b9fa82f7b completed May 8, 2026, 10:14 p.m.
Created at: May 1, 2026, 1:35 a.m.