Triple
T17006602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hundred Family Surnames |
E412586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Song dynasty text |
C37685
|
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: Song dynasty text Context triple: [Hundred Family Surnames, instanceOf, Song dynasty text]
-
A.
Song dynasty Zen text
A Song dynasty Zen text is a written work produced during China’s Song dynasty (960–1279) that records, systematizes, or comments on Chan (Zen) Buddhist teachings, practices, and dialogues.
-
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.
printing dynasty
A printing dynasty is a family-run enterprise spanning multiple generations that specializes in the production, innovation, and dissemination of printed materials, often shaping cultural, intellectual, or commercial landscapes over time.
-
D.
Yuan dynasty era
The Yuan dynasty era refers to the period (1271–1368) when the Mongol-led Yuan dynasty ruled China, marked by vast Eurasian integration, cultural exchange, and significant developments in administration, trade, and the arts.
-
E.
Twenty-Four Histories
The Twenty-Four Histories are the core set of official Chinese dynastic histories, compiled over many centuries to record the political, social, and cultural narratives of successive imperial dynasties from earliest times through the Ming.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:32 a.m.