Triple
T38661836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dzungar genocide |
E940353
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Central Asian history |
C65496
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in Central Asian history Context triple: [Dzungar genocide, instanceOf, event in Central Asian history]
-
A.
event in the Ottoman Empire
An event in the Ottoman Empire is any significant occurrence—political, military, social, economic, or cultural—that took place within or directly affected the Ottoman state and its territories during its existence.
-
B.
historical event in China
A historical event in China is a significant occurrence or series of occurrences within Chinese territory or involving Chinese society that has had a notable impact on the country's political, social, cultural, or economic development.
-
C.
8th-century historical event
An 8th-century historical event is a significant occurrence between 700 and 799 CE that influenced the political, social, cultural, or religious development of societies during that period.
-
D.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
-
E.
event in Serbian history
A significant occurrence or development within the historical timeline of Serbia that influenced its political, social, cultural, or territorial evolution.
- F. None of above. chosen
Provenance (1 batch)
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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:33 p.m.