Triple
T8162845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Chenghuang Miao |
E190616
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 上海城隍庙 |
E36136
|
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: [Shanghai Chenghuang Miao, hasChineseName, 上海城隍庙]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 上海城隍庙 Context triple: [Shanghai Chenghuang Miao, hasChineseName, 上海城隍庙]
-
A.
太庙
太庙是北京故宫东侧一座明清皇家宗庙建筑群，现为对公众开放的历史文化景区。
-
B.
外滩
外滩是位于中国上海黄浦江西岸、以万国建筑群和城市天际线景观著称的历史性滨水区域与著名旅游地标。
-
C.
佛香阁
佛香阁是位于北京颐和园万寿山上的标志性古建筑，也是清代皇家园林中最著名的佛教建筑之一。
-
D.
Jiading Confucian Temple
Jiading Confucian Temple is a historic Confucian temple complex in Shanghai renowned for its traditional architecture and cultural significance as a center of Confucian learning and local heritage.
-
E.
City God Temple of Shanghai
chosen
The City God Temple of Shanghai is a historic Taoist temple and popular cultural landmark in Shanghai’s Old City, renowned for its traditional architecture, bustling marketplace, and role as a center of local folk worship.
- 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_69ca82c0ef14819083713f4473dd847c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4557ebc88190b4e2cab258374d23 |
completed | March 31, 2026, 3:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ccbf35000c8190ba78f69b7b1290e8 |
completed | April 1, 2026, 6:46 a.m. |
Created at: March 30, 2026, 5:38 p.m.