Triple
T8148031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Jin dynasty |
E190262
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Chang’an |
E155222
|
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: Chang’an | Statement: [Western Jin dynasty, capital, Chang’an]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Chang’an Context triple: [Western Jin dynasty, capital, Chang’an]
-
A.
Chang'an
chosen
Chang'an was the ancient capital of several Chinese dynasties and a major political, cultural, and trade center along the Silk Road.
-
B.
Đông Đô
Đông Đô was a historical name for the city now known as Hanoi, which has long served as a major political and cultural center of Vietnam.
-
C.
Xi'an
Xi'an is a major historic city in central China, famed as the eastern terminus of the Silk Road and home to the Terracotta Army of Emperor Qin Shi Huang.
-
D.
Yuan Dadu
Yuan Dadu was the capital city of the Yuan dynasty in China, located on the site of present-day Beijing and serving as a major political and cultural center of the Mongol-ruled empire.
-
E.
Zhongdu
Zhongdu was the historical capital city of the Jurchen-led Jin dynasty in northern China, located in what is now part of modern Beijing.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb447e74e081908df774edb2134209 |
completed | March 31, 2026, 3:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde71b7688819096b2d30a37a8a00b |
completed | April 2, 2026, 3:48 a.m. |
Created at: March 30, 2026, 5:36 p.m.