Triple

T20440963
Position Surface form Disambiguated ID Type / Status
Subject Toghrul III E501388 entity
Predicate givenName P17 FINISHED
Object Toghrul 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: Toghrul | Statement: [Toghrul III, givenName, Toghrul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Toghrul
Context triple: [Toghrul III, givenName, Toghrul]
  • A. Toghrul II
    Toghrul II was a 12th-century Seljuk sultan who briefly ruled parts of western Iran during the dynasty’s period of fragmentation and decline.
  • B. Toghrul III chosen
    Toghrul III was the last sultan of the Great Seljuk Empire, whose defeat and death in 1194 marked the effective end of Seljuk political power in Persia.
  • C. Toghrul Beg
    Toghrul Beg was the 11th-century Turkic leader who established Seljuk power in the Islamic world and became the first sultan of the Seljuk dynasty.
  • D. Toghrul (Wang Khan)
    Toghrul (Wang Khan) was a powerful Kerait khan and early ally-turned-rival of Genghis Khan who played a key role in the rise of the Mongol Empire.
  • E. Kuchum Khan
    Kuchum Khan was the last khan of the Siberian Khanate, known for resisting Russian expansion into Siberia in the late 16th century.
  • 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_69e0b4ab3cfc8190ac9bf32e932316b1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e685f2e8888190a2e0d6b2bf6c905d completed April 20, 2026, 8 p.m.
Created at: April 16, 2026, 11:31 a.m.