Triple
T28755796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ming Shilu |
E731667
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese historical source |
C6136
|
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 historical source Context triple: [Ming Shilu, instanceOf, Chinese historical source]
-
A.
historical source
chosen
A historical source is any original material—such as documents, artifacts, recordings, or testimonies—created in the past that provides evidence or information about historical events, people, or conditions.
-
B.
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.
-
C.
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.
-
D.
Korean historical document
A Korean historical document is an original written or printed record produced in or about Korea’s past, preserving information on its political, social, cultural, or intellectual history.
-
E.
Warring States–period manuscript
A Warring States–period manuscript is an ancient Chinese written document, typically inscribed on bamboo or silk between the 5th and 3rd centuries BCE, that preserves contemporary philosophical, political, legal, or literary texts from the era of competing states before imperial unification.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
Created at: April 28, 2026, 6:09 a.m.