Triple
T10109984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 湘语 |
E218213
|
entity |
| Predicate | majorCityWhereSpoken |
P35609
|
FINISHED |
| Object | 衡阳市 |
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: 衡阳市 | Statement: [湘语, majorCityWhereSpoken, 衡阳市]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 衡阳市 Context triple: [湘语, majorCityWhereSpoken, 衡阳市]
-
A.
浏阳
浏阳是中国湖南省东部的一座县级市，以烟花爆竹产业和红色革命历史而闻名。
-
B.
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.
-
C.
Yongzhou
Yongzhou is a prefecture-level city in southern Hunan Province, China, known for its long history and location at the confluence of the Xiang and Xiao rivers.
-
D.
Xiangxiang City
Xiangxiang City is a county-level city in Hunan Province, China, administered by the prefecture-level city of Xiangtan and known for its historical and cultural heritage.
-
E.
Chenzhou
Chenzhou is a prefecture-level city in southern Hunan Province, China, known as a regional transport hub and for its rich mineral resources and scenic mountainous landscapes.
- 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_69d3005e007881909f40575d129f2c3d |
completed | April 6, 2026, 12:37 a.m. |
Created at: March 30, 2026, 9:03 p.m.