Triple
T12210721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chu–Han Contention |
E290948
|
entity |
| Predicate | opponent |
P437
|
FINISHED |
| Object | Chu |
E710001
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Chu | Statement: [Chu–Han Contention, opponent, Chu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chu Context triple: [Chu–Han Contention, opponent, Chu]
-
A.
Chu
chosen
Chu was a powerful ancient Chinese state during the Spring and Autumn and Warring States periods, known for its distinctive culture, military strength, and significant role in early Chinese history.
-
B.
Chu
Chu is a major river in Central Asia that flows through Kyrgyzstan and Kazakhstan, playing an important role in regional agriculture and water supply.
-
C.
Chu
Chu is a Chinese surname borne by numerous notable individuals across politics, science, arts, and entertainment.
-
D.
Chau
Chau is a romanized surname and given name of Chinese and Vietnamese origin, commonly used as a variant spelling of Zhao and several other East Asian names.
-
E.
Chō
Chō is a Japanese surname borne by various notable individuals across fields such as the military, arts, and entertainment.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91c7ed4688190b0546b784e36b0ec |
completed | April 10, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e5666f48190a28eed761e7b9210 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:51 p.m.