Triple
T27541799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Scribe’s Records |
E695255
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese historiographical work |
C13788
|
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: Chinese historiographical work Context triple: [Grand Scribe’s Records, instanceOf, Chinese historiographical work]
-
A.
ancient Chinese political treatise
An ancient Chinese political treatise is a classical written work that systematically expounds theories, principles, and strategies for governing the state, managing officials, and maintaining social order within the historical context of imperial China.
-
B.
Chinese historical novel
A Chinese historical novel is a long-form narrative that dramatizes events, figures, and social conditions from China’s past, blending historical fact with literary imagination to explore cultural, political, and moral themes.
-
C.
historiographical work
chosen
A historiographical work is a scholarly study that analyzes how historical events, periods, or themes have been interpreted, debated, and written about by historians over time.
-
D.
Chinese historical event
A Chinese historical event is a significant occurrence in China’s past—such as a war, reform, revolution, treaty, or cultural milestone—that shaped the political, social, economic, or cultural development of Chinese civilization.
-
E.
section of historical work
A section of historical work is a distinct, thematically organized subdivision of a larger historical text that presents and analyzes specific events, periods, or topics within the broader narrative.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 27, 2026, 1:31 p.m.