Triple
T12650943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 韓国統監 |
E302155
|
entity |
| Predicate | 所在地 |
P40
|
FINISHED |
| Object | 京城 |
E2312
|
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: [韓国統監, 所在地, 京城]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 京城 Context triple: [韓国統監, 所在地, 京城]
-
A.
北京皇城
北京皇城是明清两代北京城中围绕皇宫设置的内城区域，汇集重要宫殿、坛庙和皇家建筑群的核心防御与礼制空间。
-
B.
Yuan Dadu
Yuan Dadu was the capital city of the Yuan dynasty in China, located on the site of present-day Beijing and serving as a major political and cultural center of the Mongol-ruled empire.
-
C.
Beijing
chosen
Beijing is the capital city of China, a major political, cultural, and economic center known for its rich history and rapid modern development.
-
D.
Tiāntán
Tiāntán is the Chinese pinyin name for the Temple of Heaven, a historic imperial religious complex in Beijing where Ming and Qing dynasty emperors performed annual ceremonies to pray for good harvests.
-
E.
Yingchang, Beiping
Yingchang, Beiping was a locality in the Beiping (Beijing) region of Ming China notable as the birthplace of the Yongle Emperor.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9615f28cc81908e37249d7ab5ed74 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6687dad6c8190bb72bfebf6636a37 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:18 p.m.