Triple

T19425123
Position Surface form Disambiguated ID Type / Status
Subject Ilghazi E485960 entity
Predicate successor P78 FINISHED
Object Timurtash 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: Timurtash | Statement: [Ilghazi, successor, Timurtash]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Timurtash
Context triple: [Ilghazi, successor, Timurtash]
  • A. Timurtash chosen
    Timurtash was a prominent Artuqid ruler and military leader in the medieval Islamic world.
  • B. Timur
    Timur is a deposed Tatar king and the blind, exiled father of Prince Calaf in Giacomo Puccini’s opera "Turandot."
  • C. Timur
    Timur, also known as Tamerlane, was a 14th-century Turco-Mongol conqueror who founded the Timurid Empire in Central Asia and became one of history’s most formidable military leaders.
  • D. Timuri
    Timuri are a small ethnic group in Afghanistan and Iran, traditionally semi-nomadic and known for their distinct dialect and cultural practices within the broader Aimaq community.
  • E. Ulugh Khan
    Ulugh Khan was the earlier title of Ghiyas ud din Balban, a powerful 13th-century Sultan of Delhi known for his strict rule and military strength.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e8d688f881909c85104a62e09d8a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e63217bd2c81909e216e13aa4c487d completed April 20, 2026, 2:03 p.m.
Created at: April 10, 2026, 1:37 p.m.