Triple
T9886938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ningxiang |
E180955
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Hunan |
E30061
|
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: Hunan | Statement: [Ningxiang, region, Hunan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hunan Context triple: [Ningxiang, region, Hunan]
-
A.
Hunan Province
chosen
Hunan Province is a landlocked region in south-central China known for its strategic location, spicy cuisine, and role as a major battleground and revolutionary base in modern Chinese history.
-
B.
Hubei Province
Hubei Province is a landlocked region in central China known for its capital city Wuhan, major role in industry and transportation, and significant historical and cultural heritage.
-
C.
Kansu
Kansu is a Turkish surname most notably associated with Şevket Aziz Kansu, a prominent Turkish academic and anthropologist.
-
D.
northwestern Hunan
Northwestern Hunan is a subregion of China’s Hunan Province characterized by its inland location, river plains, and a mix of urban centers and agricultural areas.
-
E.
Jianxi
Jianxi was an era name used during the reign of Emperor Ling of the Eastern Han dynasty in ancient China.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb457c8cc81909d211d5882228076 |
completed | April 2, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d15df30819092ae896786564478 |
completed | April 5, 2026, 10:44 a.m. |
Created at: March 30, 2026, 8:38 p.m.