Triple
T29970188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mun of Balhae |
E761294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Balhae monarch |
C18267
|
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: Balhae monarch Context triple: [King Mun of Balhae, instanceOf, Balhae monarch]
-
A.
Korean king
chosen
A Korean king is the sovereign ruler of a Korean dynasty, responsible for governing the kingdom, upholding Confucian ideals, overseeing military and diplomatic affairs, and serving as the symbolic and political head of state.
-
B.
Korean emperor
A Korean emperor is the supreme hereditary monarch who holds the highest sovereign authority over a unified Korean state, historically or in a conceptual context.
-
C.
Jin state ruler
A Jin state ruler is the sovereign leader of the ancient Chinese state of Jin, responsible for governing its territories, commanding its military, and managing its political and diplomatic affairs during the Zhou dynasty period.
-
D.
King of Anshan
The "King of Anshan" is a conceptual class representing the sovereign ruler of the ancient Elamite city-state of Anshan, embodying political authority, territorial control, and dynastic legitimacy within that historical context.
-
E.
Ahom king
An Ahom king was the hereditary monarch of the Ahom dynasty in Assam, who ruled the kingdom, led military campaigns, oversaw administration, and patronized religion and culture from the 13th to the early 19th century.
- F. None of above.
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_69f22467626081908d5afea489590e96 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:31 p.m.