Triple
T14978451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taohuayuan (Peach Blossom Spring) scenic area |
E373512
|
entity |
| Predicate | ChineseName |
P744
|
FINISHED |
| Object | 桃花源风景区 |
E373512
|
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: [Taohuayuan (Peach Blossom Spring) scenic area, ChineseName, 桃花源风景区]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 桃花源风景区 Context triple: [Taohuayuan (Peach Blossom Spring) scenic area, ChineseName, 桃花源风景区]
-
A.
Taohuayuan (Peach Blossom Spring) scenic area
chosen
Taohuayuan (Peach Blossom Spring) scenic area is a famous tourist destination in Changde, Hunan, inspired by Tao Yuanming’s classic fable and known for its idyllic landscapes, cultural heritage, and poetic atmosphere.
-
B.
武当山
武当山是位于中国湖北省的著名道教名山和世界文化遗产,以其古建筑群和武当武术而闻名。
-
C.
本栖湖
本栖湖は、富士五湖の一つとして知られる山梨県の淡水湖で、透明度の高い湖水と富士山を望む景観で有名な観光地です。
-
D.
颐和园
颐和园是位于北京市西北部、以宏伟的皇家园林建筑和昆明湖、万寿山自然景观著称的世界文化遗产。
-
E.
Shaoshan Scenic Area
Shaoshan Scenic Area is a famous red tourism destination in Hunan, China, centered around the birthplace and memorial sites of Mao Zedong amid a mountainous rural landscape.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fbd138819092254ea37388026c |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe8beca6d88190a0c1adb18c9f2ac4 |
completed | May 9, 2026, 1:20 a.m. |
Created at: April 10, 2026, 2:51 a.m.