Triple
T10109909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hsn |
E218212
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object | Hengyang Xiang |
E168458
|
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: Hengyang Xiang | Statement: [hsn, hasDialect, Hengyang Xiang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hengyang Xiang Context triple: [hsn, hasDialect, Hengyang Xiang]
-
A.
Liling Xiang
Liling Xiang is a regional Chinese dialect spoken in and around Liling in Hunan Province.
-
B.
Ningxiang
Ningxiang is a county-level city in Hunan Province, China, administered by the prefecture-level city of Changsha and known for its rapidly developing economy and rich cultural heritage.
-
C.
Hengyang
chosen
Hengyang is a major industrial and transportation hub city in southern China, located along the Xiang River in the south of Hunan Province.
-
D.
Huaihua
Huaihua is a prefecture-level city in southwestern Hunan Province, China, known as a regional transportation hub and home to several ethnic minority communities.
-
E.
Shaoyang Old Xiang
Shaoyang Old Xiang is a regional variety of the Old Xiang branch of Chinese spoken in and around Shaoyang in Hunan Province.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cdb3c88190a74f75bf865664f3 |
completed | April 2, 2026, 2:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6a7bbfdb0819080377d3402bcfec3 |
completed | April 8, 2026, 7:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.