Triple
T14917224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiang’an District, Wuhan |
E371410
|
entity |
| Predicate | hasChineseName |
P4878
|
FINISHED |
| Object | 江岸区 |
E371410
|
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: [Jiang’an District, Wuhan, hasChineseName, 江岸区]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 江岸区 Context triple: [Jiang’an District, Wuhan, hasChineseName, 江岸区]
-
A.
汉阳
汉阳是中国湖北省武汉市的一个历史悠久的城区，位于长江与汉江交汇处，以其工业基础和文化遗产而闻名。
-
B.
下陆区
下陆区 is an urban district of Huangshi City in Hubei Province, China, known for its industrial base and role in the city’s economic development.
-
C.
黄石港区
黄石港区 is an urban district of Huangshi City in Hubei Province, China, known as one of the city’s central administrative and commercial areas along the Yangtze River.
-
D.
Jianghan District
Jianghan District is a central urban district of Wuhan, Hubei Province, known for its commercial hubs and historical and cultural sites.
-
E.
Jiang’an District, Wuhan
chosen
Jiang’an District is a central urban district of Wuhan, China, known for its historic riverfront along the Yangtze and Han rivers and its legacy as part of the former foreign concession area in Hankou.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62038508190946499cd3552990e |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72bf2120819099df39bdc1da691b |
completed | May 8, 2026, 11:33 p.m. |
Created at: April 10, 2026, 2:32 a.m.