Triple
T9153163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Red Cliffs |
E219639
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in Chinese history |
C13438
|
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: event in Chinese history Context triple: [Battle of Red Cliffs, instanceOf, event in Chinese history]
-
A.
revolutionary event in China
A revolutionary event in China is a significant historical occurrence involving organized collective action aimed at fundamentally transforming the country’s political, social, or economic structures.
-
B.
era in Chinese history
An era in Chinese history is a distinct period marked by characteristic political structures, cultural developments, social changes, and significant events that differentiate it from other historical periods in China.
-
C.
event in Myanmar history
An event in Myanmar history is a significant occurrence or development within Myanmar’s past that has shaped its political, social, cultural, or economic trajectory.
-
D.
event in ancient history
chosen
An event in ancient history is a significant occurrence or series of actions that took place in early human civilizations and has had a lasting impact on cultural, political, or social development.
-
E.
Japanese historical event
A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 7:20 p.m.