Triple

T16837168
Position Surface form Disambiguated ID Type / Status
Subject Dzungar people E409312 entity
Predicate notableLeader P304 FINISHED
Object Amursana 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: Amursana | Statement: [Dzungar people, notableLeader, Amursana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Amursana
Context triple: [Dzungar people, notableLeader, Amursana]
  • A. Amursana chosen
    Amursana was an 18th-century Oirat (Dzungar) prince and military leader known for his pivotal role in the Dzungar–Qing conflicts and his eventual rebellion against Qing rule in Central Asia.
  • B. Batu Khan
    Batu Khan was a 13th-century Mongol ruler and military commander who founded the Golden Horde and led the Mongol invasions of Eastern Europe.
  • C. Alpamys Batyr
    Alpamys Batyr is a legendary Turkic folk hero celebrated in Central Asian epic poetry for his bravery, strength, and defense of his people.
  • D. Erlik Khan
    Erlik Khan is a deity from Turkic and Mongolic mythology, commonly regarded as the god of death and ruler of the underworld.
  • E. Bayanchur Khan
    Bayanchur Khan was an 8th-century ruler who greatly expanded and consolidated the Uyghur Khaganate, turning it into a powerful Central Asian empire.
  • 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_69d883952b048190887740a980b712ed completed April 10, 2026, 4:59 a.m.
NER Named-entity recognition batch_69e3b34e080c8190bf7a236205b41db2 completed April 18, 2026, 4:37 p.m.
Created at: April 10, 2026, 5:23 a.m.