Triple
T15425813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sartaq Khan |
E369505
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | Ulaqchi |
E344017
|
NE 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: Ulaqchi | Statement: [Sartaq Khan, successor, Ulaqchi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulaqchi Context triple: [Sartaq Khan, successor, Ulaqchi]
-
A.
Ulaghchi
chosen
Ulaghchi was a short-reigning 13th-century khan of the Golden Horde, likely a grandson of Genghis Khan, who briefly ruled following Batu Khan’s death.
-
B.
Yura
Yura is a common Slavic diminutive form of the male given name Yuri (or Yuriy), often used as a familiar or affectionate nickname.
-
C.
Uchali
Uchali, also known as Uluch Ali, was a prominent 16th-century Ottoman admiral and corsair who rose from captivity to become Kapudan Pasha (grand admiral) of the Ottoman fleet.
-
D.
Ulyana
Ulyana is a feminine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Tanasi
Tanasi was a historic Overhill Cherokee town in present-day Tennessee that gave the state its name and served as an early political center for the Cherokee.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec1fb288190a3625b8e4f487dd1 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff1a7ed0ec8190b8086f78df965b61 |
completed | May 9, 2026, 11:29 a.m. |
Created at: April 10, 2026, 3:20 a.m.