Triple
T16138235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhongdu |
E391585
|
entity |
| Predicate | predecessorCapital |
P3417
|
FINISHED |
| Object | Shangjing |
E392282
|
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: Shangjing | Statement: [Zhongdu, predecessorCapital, Shangjing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shangjing Context triple: [Zhongdu, predecessorCapital, Shangjing]
-
A.
Shangjing
chosen
Shangjing was the principal early capital city of China’s Jurchen-led Jin dynasty, serving as a key political and administrative center in northeastern China.
-
B.
Shangjing
Shangjing was the principal imperial capital city of the Khitan-led Liao dynasty in what is now northeastern China.
-
C.
Haojing
Haojing was the primary western capital city of the early Zhou dynasty in ancient China, located near present-day Xi’an.
-
D.
Xintai
Xintai is a county-level city in Shandong Province, China, administered by the prefecture-level city of Tai'an.
-
E.
Hejin
Hejin is a county-level city in southern Shanxi Province, China, situated along the Fen River near its confluence with the Yellow River.
- 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_69d87f1bb0988190b490d273dbf3fd03 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21a05e68881908319454a478cdda5 |
completed | April 17, 2026, 11:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff2b574148190b9d5b725d7d113af |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 5:01 a.m.