Triple
T16900155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koko Nor |
E424412
|
entity |
| Predicate | hasIsland |
P970
|
FINISHED |
| Object | Haixin Shan |
E1239340
|
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: Haixin Shan | Statement: [Koko Nor, hasIsland, Haixin Shan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haixin Shan Context triple: [Koko Nor, hasIsland, Haixin Shan]
-
A.
Haixin Shan
chosen
Haixin Shan is a small island located within Qinghai Lake on the northeastern Tibetan Plateau in China.
-
B.
Huaying Mountain
Huaying Mountain is a scenic mountainous area in Sichuan Province, China, known for its natural landscapes, red tourism sites, and cultural significance.
-
C.
Liushi Shan
Liushi Shan is a prominent high-altitude peak in western China, recognized as the highest summit in the Kunlun Mountains range.
-
D.
Xueshan
Xueshan is a prominent mountain in Taiwan known for its high elevation, alpine scenery, and popularity among hikers and mountaineers.
-
E.
Wanshou Shan
Wanshou Shan, also known as Longevity Hill, is a prominent, scenic hill within Beijing’s Summer Palace complex, famed for its historic temples, pavilions, and panoramic views over Kunming Lake.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dbc6e48190be90066b82fc61db |
completed | April 18, 2026, 6:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfcd0db8819080d415a18b3435e2 |
completed | May 10, 2026, 6:34 p.m. |
Created at: April 10, 2026, 5:29 a.m.