Triple
T8115158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Huizong of Song |
E189453
|
entity |
| Predicate | deathPlace |
P21
|
FINISHED |
| Object | Wuguocheng |
E389351
|
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: Wuguocheng | Statement: [Emperor Huizong of Song, deathPlace, Wuguocheng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wuguocheng Context triple: [Emperor Huizong of Song, deathPlace, Wuguocheng]
-
A.
Guandu
Guandu is a district in northern Taipei, Taiwan, known for its riverside wetlands, hot springs, and the historic Guandu Temple.
-
B.
Licheng
Licheng is the courtesy name of the Daoguang Emperor, a Qing dynasty ruler of China in the early 19th century.
-
C.
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.
-
D.
Longcheng
chosen
Longcheng was the principal royal city and political center of the Xiongnu confederation in ancient Inner Asia.
-
E.
Dongjing
Dongjing is the historical name for Kaifeng when it served as the capital of the Northern Song dynasty in China.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb43308e0081909ea0463dabd74e4d |
completed | March 31, 2026, 3:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce0218a3888190a0b224cf93a511de |
completed | April 2, 2026, 5:43 a.m. |
Created at: March 30, 2026, 5:33 p.m.