Triple

T37027211
Position Surface form Disambiguated ID Type / Status
Subject Rhazates E916386 entity
Predicate roleAtBattleOfNineveh P188159 FINISHED
Object overall Sasanian field commander 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: overall Sasanian field commander | Statement: [Rhazates, roleAtBattleOfNineveh, overall Sasanian field commander]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfNineveh
Context triple: [Rhazates, roleAtBattleOfNineveh, overall Sasanian field commander]
  • A. roleAtKarbala
    Indicates the specific role, position, or function an entity held in relation to the events of the Battle of Karbala.
  • B. hasRoleInAncientMesopotamia
    Indicates that an entity held a specific social, political, religious, or occupational role within the context of ancient Mesopotamian society.
  • C. roleInBosporanKingdom
    Indicates that an entity held a specific position, function, or office within the political or social structure of the Bosporan Kingdom.
  • D. roleAtBattleOfUhud
    Indicates the specific role, position, or function an entity held or performed during the Battle of Uhud.
  • E. statusAfterAssyrianConquest
    Indicates the condition or standing of an entity following the Assyrian conquest.
  • 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_69f76e92c7648190bcfa277f64c71a21 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fba2877b248190a974eb092243c0c4 completed May 6, 2026, 8:20 p.m.
PD Predicate disambiguation batch_69fb8d06a1b48190a937aa410d159dfa completed May 6, 2026, 6:48 p.m.
PDg Predicate description generation batch_69fba28684208190921694f23e350c3b completed May 6, 2026, 8:20 p.m.
Created at: May 3, 2026, 4:14 p.m.