Triple
T17948229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tughril |
E448760
|
entity |
| Predicate | alsoKnownAs |
P39
|
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: [Tughril, alsoKnownAs, Toghrul]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Toghrul Context triple: [Tughril, alsoKnownAs, Toghrul]
-
A.
Toghrul III
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.
-
B.
Toghrul Beg
chosen
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.
-
C.
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.
-
D.
Kuchum Khan
Kuchum Khan was the last khan of the Siberian Khanate, known for resisting Russian expansion into Siberia in the late 16th century.
-
E.
Erlik Khan
Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4afa9cb2481908c95f8c430dcc0aa |
completed | April 19, 2026, 10:34 a.m. |
Created at: April 10, 2026, 10:21 a.m.