Triple
T16060931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yehenara |
E389607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Manchu noble clan |
C36914
|
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: Manchu noble clan Context triple: [Yehenara, instanceOf, Manchu noble clan]
-
A.
Mongol royal house
The Mongol royal house is the ruling lineage descended from Genghis Khan that governed the Mongol Empire and its successor states, holding supreme political, military, and symbolic authority over Mongol domains.
-
B.
Mongol noble
A Mongol noble is a high-ranking member of Mongol society, typically belonging to ruling or aristocratic lineages, who holds political, military, and economic power within the Mongol Empire or its successor states.
-
C.
Mongol imperial dynasty branch
A Mongol imperial dynasty branch is a distinct ruling line or subdivision of the broader Mongol imperial family that governed a specific territory or khanate while sharing common ancestry and political heritage with the main Mongol Empire.
-
D.
Jurchen-led state
A Jurchen-led state is a political entity in which the Jurchen people hold primary ruling authority, shaping its governance, military organization, and cultural policies.
-
E.
Mongolic people
Mongolic people are an ethno-linguistic group originating from the Mongolian Plateau, historically associated with nomadic pastoralism and the Mongol Empire, and today encompassing various Mongol-speaking populations across Mongolia, China, Russia, and neighboring regions.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.