Triple
T16245364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Shizong of Jin |
E394357
|
entity |
| Predicate | capitalDuringReign |
P9119
|
FINISHED |
| Object | Yanjing |
E1197391
|
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: Yanjing | Statement: [Emperor Shizong of Jin, capitalDuringReign, Yanjing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yanjing Context triple: [Emperor Shizong of Jin, capitalDuringReign, Yanjing]
-
A.
Yanjing
chosen
Yanjing was a historic Chinese capital city, best known as the former name of modern-day Beijing.
-
B.
Xinjing
Xinjing was the capital city of the Japanese puppet state of Manchukuo in northeastern China during the 1930s and early 1940s.
-
C.
Yiheyuan
Yiheyuan, known in English as the Summer Palace, is a vast imperial garden and former royal retreat in Beijing famed for its lakes, palaces, and classical Chinese landscape design.
-
D.
Dajing
Dajing is a Chinese given name notably borne by Olympic short track speed skating champion Wu Dajing.
-
E.
Jūyōngguān
Jūyōngguān is a historically significant mountain pass and fortified section of the Great Wall of China located northwest of 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e24561d250819096f709ea8751fcb9 |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c48c5cc8190ba99154e99942316 |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:04 a.m.