Triple
T9667941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haojing |
E233751
|
entity |
| Predicate | ChineseName |
P744
|
FINISHED |
| Object | 鎬京 |
E233751
|
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: [Haojing, ChineseName, 鎬京]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 鎬京 Context triple: [Haojing, ChineseName, 鎬京]
-
A.
Hanseong
Hanseong was the historical name for Seoul when it served as the capital of the Joseon Dynasty in Korea.
-
B.
Suwon
Suwon is a major South Korean city best known for its UNESCO-listed Hwaseong Fortress and as a key cultural and economic center just south of Seoul.
-
C.
Hanyang
Hanyang is a historic district and former city now incorporated into Wuhan in Hubei Province, China, known for its early industrial development and strategic location at the confluence of the Han and Yangtze rivers.
-
D.
Haojing
chosen
Haojing was the primary western capital city of the early Zhou dynasty in ancient China, located near present-day Xi’an.
-
E.
Kaesong
Kaesong is a historic city in present-day North Korea that served as the capital of the medieval Korean kingdom of Goryeo and remains known for its cultural heritage and traditional architecture.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a208798819088db055e44d288e3 |
completed | April 4, 2026, 10:01 p.m. |
Created at: March 30, 2026, 8:15 p.m.