Triple
T8420987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiling Gorge |
E198848
|
entity |
| Predicate | hasNameInChinese |
P4878
|
FINISHED |
| Object | 西陵峡 |
E198848
|
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: [Xiling Gorge, hasNameInChinese, 西陵峡]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 西陵峡 Context triple: [Xiling Gorge, hasNameInChinese, 西陵峡]
-
A.
朝天门
朝天门 is a historic and iconic riverfront gate area in Chongqing, China, located at the confluence of the Yangtze and Jialing rivers and known today as a major transportation and commercial hub.
-
B.
Qutang Gorge
Qutang Gorge is the shortest and narrowest of China’s famed Three Gorges on the Yangtze River, renowned for its dramatic cliffs and spectacular river scenery.
-
C.
Xiling Gorge
chosen
Xiling Gorge is the easternmost and longest of China’s Three Gorges on the Yangtze River, known for its dramatic cliffs, treacherous shoals, and scenic river landscapes.
-
D.
富春江
富春江是中国浙江省境内一条以秀丽山水风光和人文景观著称的重要河流与旅游胜地。
-
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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84ca7b348190abab25e79b05407f |
completed | March 31, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce035279f48190861b97167fa3882c |
completed | April 2, 2026, 5:49 a.m. |
Created at: March 30, 2026, 6:06 p.m.