Triple
T15075433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hongwu Code |
E379987
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ming dynasty law code |
C23617
|
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: Ming dynasty law code Context triple: [Hongwu Code, instanceOf, Ming dynasty law code]
-
A.
Chinese legal code
chosen
A Chinese legal code is a systematically organized collection of laws and regulations that defines legal norms, rights, obligations, and penalties within a Chinese jurisdiction.
-
B.
Yuan dynasty court
The Yuan dynasty court was the central governing institution of the Mongol-ruled Chinese empire, where the emperor and his officials conducted political, military, and ceremonial affairs that integrated Mongol and Chinese traditions.
-
C.
Malacca Sultanate law code
The Malacca Sultanate law code is a historical legal framework that governed political authority, trade, social conduct, and Islamic practices in the Malacca Sultanate, serving as a foundational reference for later Malay legal traditions.
-
D.
Ming dynasty architecture
Ming dynasty architecture is a style of Chinese building characterized by strict symmetry, axial layouts, timber-frame construction with bracket sets (dougong), raised platforms, and elaborately decorated roofs with glazed tiles, reflecting imperial authority and Confucian order.
-
E.
Ming dynasty emperor
A Ming dynasty emperor is the supreme hereditary ruler of China during the Ming period (1368–1644), wielding ultimate political, military, and ritual authority as the Son of Heaven within a centralized bureaucratic state.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:02 a.m.