Triple

T32224793
Position Surface form Disambiguated ID Type / Status
Subject Battle of Hyelion and Leimocheir E823164 entity
Predicate SeljukCommander P73299 FINISHED
Object Atabeg of the Sultan of Rum NE NERFINISHED

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: Atabeg of the Sultan of Rum | Statement: [Battle of Hyelion and Leimocheir, SeljukCommander, Atabeg of the Sultan of Rum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: SeljukCommander
Context triple: [Battle of Hyelion and Leimocheir, SeljukCommander, Atabeg of the Sultan of Rum]
  • A. commanderSeljuk chosen
    Indicates that one entity served as a military commander within the Seljuk context (e.g., army, campaign, or polity) for the other entity.
  • B. OttomanCommander
    Indicates that an entity serves in the role of a military commander within the Ottoman Empire.
  • C. MamlukCommander
    Indicates that an entity serves as a military commander within the Mamluk political or military structure in relation to another entity or context.
  • D. AbbasidCommander
    Indicates that the subject serves as a military commander for, or in association with, the Abbasid Caliphate.
  • E. ArabCommander
    Indicates that the subject serves as a military commander associated with Arab forces or entities.
  • 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_69f3490b4f948190b99e4f999f5be25f completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bbcb07ec81909e1d6c7eb24fbdd7 completed May 3, 2026, 3:06 a.m.
PD Predicate disambiguation batch_69f6b6293188819080d5041ca0adb969 completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:38 a.m.