Triple
T18238522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 晴川阁 |
E436744
|
entity |
| Predicate | 文化属性 |
P81632
|
FINISHED |
| Object | 历史文化名楼 |
—
|
NE NERFINISHED |
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.
名城
名城 is the Japanese name for Meijō, commonly associated with Meijo University and the surrounding Meijō area in Nagoya, Japan.
-
B.
城门楼
城门楼是一种建于城门之上的多层楼阁式建筑,兼具防御、瞭望与礼仪象征等功能,在中国古代城池与宫城中极具代表性。
-
C.
National Famous Historical and Cultural City of China
chosen
The National Famous Historical and Cultural City of China is an official designation granted by the Chinese government to cities recognized for their significant historical heritage, cultural value, and well-preserved traditional architecture.
-
D.
黄鹤楼
黄鹤楼是位于中国湖北省武汉市长江南岸蛇山之巅的历史名楼,以其悠久的文化底蕴和壮丽的江景闻名于世。
-
E.
Shanghai Excellent Historical Building
Shanghai Excellent Historical Building is an official municipal designation in Shanghai for architecturally and historically significant structures that are protected for their cultural value.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b91104e08190a8241f7d260a5162 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f7e0a0ac819090d48ae45b1ebfc9 |
completed | April 19, 2026, 3:42 p.m. |
Created at: April 10, 2026, 10:33 a.m.