Triple
T16514350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Pass Under Heaven |
E401143
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 天下第一关 |
E92072
|
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: [First Pass Under Heaven, hasChineseName, 天下第一关]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 天下第一关 Context triple: [First Pass Under Heaven, hasChineseName, 天下第一关]
-
A.
居庸关
居庸关是位于北京西北部、长城要冲之一的著名古代关隘和军事防御要地。
-
B.
朝天门
朝天门 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.
-
C.
Jinshanling Great Wall
Jinshanling Great Wall is a well-preserved and scenic section of China's Great Wall, renowned for its dense concentration of watchtowers and dramatic mountain views.
-
D.
Shanhaiguan Pass
chosen
Shanhaiguan Pass is a historically significant fortified mountain pass in northeastern China that marks the eastern terminus of the Great Wall and long served as a strategic gateway between China’s heartland and Manchuria.
-
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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7a5ff88190984e2f2bc2fd17cc |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006084949081909e8cdfeafa7564de |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:14 a.m.