Triple
T13310898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ᠬᠣᠸᠠᠬᠣᠲᠠ |
E317060
|
entity |
| Predicate | ChineseName |
P744
|
FINISHED |
| Object | 呼和浩特 |
E80543
|
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: [ᠬᠣᠸᠠᠬᠣᠲᠠ, ChineseName, 呼和浩特]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 呼和浩特 Context triple: [ᠬᠣᠸᠠᠬᠣᠲᠠ, ChineseName, 呼和浩特]
-
A.
乌兰察布市
乌兰察布市是位于中国内蒙古自治区中部、以草原风光和交通枢纽地位著称的地级市。
-
B.
Baotou
Baotou is a major industrial city in Inner Mongolia, China, known especially for its steel production and nearby rare earth mineral processing.
-
C.
Chifeng
Chifeng is a prefecture-level city in southeastern Inner Mongolia, China, known for its mix of grassland, forest, and historical sites linked to ancient nomadic cultures.
-
D.
Hohhot
chosen
Hohhot is the capital and largest city of Inner Mongolia in northern China, known as a regional center of politics, culture, and industry.
-
E.
Xilinhot
Xilinhot is a city in Inner Mongolia, China, known as an important regional center on the Xilingol grasslands with a strong pastoral and Mongolian cultural heritage.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990f56abc8190951774a999e2ce11 |
completed | April 11, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f716e7b9a48190a33b04df8ad45ed8 |
completed | May 3, 2026, 9:35 a.m. |
Created at: April 9, 2026, 9:29 p.m.