Triple
T9667453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuzhishan |
E233741
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 五指山 |
E233741
|
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: [Wuzhishan, hasChineseName, 五指山]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 五指山 Context triple: [Wuzhishan, hasChineseName, 五指山]
-
A.
Wuzhishan
chosen
Wuzhishan is a county-level city in central Hainan, China, known for its mountainous terrain and tropical rainforest environment.
-
B.
长白山
长白山是一座位于中朝边界、以火山天池和丰富自然资源闻名的著名高山与风景名胜区。
-
C.
Qianhu Mountain
Qianhu Mountain is a scenic peak located within the UNESCO-listed Three Parallel Rivers of Yunnan Protected Areas in southwestern China, known for its rugged terrain and rich biodiversity.
-
D.
Xiaoguanyin Mountain
Xiaoguanyin Mountain is a prominent volcanic peak within Taiwan’s Yangmingshan range, known for its rugged terrain and scenic hiking routes.
-
E.
六甲山地
六甲山地は、兵庫県南東部に位置し、神戸市の背後に連なる山並みとして知られる観光・レジャー地帯です。
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a208798819088db055e44d288e3 |
completed | April 4, 2026, 10:01 p.m. |
Created at: March 30, 2026, 8:15 p.m.