Triple
T11426525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiongzhou Strait |
E270763
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 琼州海峡 |
E270763
|
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: [Qiongzhou Strait, hasChineseName, 琼州海峡]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 琼州海峡 Context triple: [Qiongzhou Strait, hasChineseName, 琼州海峡]
-
A.
宗谷海峡
宗谷海峡 is the strait between Japan’s Hokkaidō and Russia’s Sakhalin Island, forming part of the boundary between the Sea of Japan and the Sea of Okhotsk and serving as an important international shipping route.
-
B.
Qiongzhou Strait
chosen
Qiongzhou Strait is a narrow body of water in southern China that separates Hainan Island from the Leizhou Peninsula on the mainland.
-
C.
巴士海峽
巴士海峽是位於台灣與菲律賓呂宋島之間、連接南海與太平洋的重要國際海峽與航運通道。
-
D.
Lingdingyang channel
Lingdingyang channel is a major waterway in the Pearl River Estuary in southern China, forming part of the busy maritime route between Hong Kong, Macau, and the mainland.
-
E.
Bohai Strait
The Bohai Strait is a strategically important waterway in northeastern China that links the semi-enclosed Bohai Sea with the larger Yellow Sea and the Pacific Ocean.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c000b88190bfaa646b2dc424b7 |
completed | April 9, 2026, 8:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e5b8c8e1988190aba5a2536dbb37cf |
completed | April 20, 2026, 5:25 a.m. |
Created at: April 8, 2026, 9:35 p.m.