Triple
T8045702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Taizong of Song |
E187544
|
entity |
| Predicate | eraNameUsed |
P2938
|
FINISHED |
| Object | Yongxi |
E727249
|
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: Yongxi | Statement: [Emperor Taizong of Song, eraNameUsed, Yongxi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yongxi Context triple: [Emperor Taizong of Song, eraNameUsed, Yongxi]
-
A.
Yongxi
chosen
Yongxi was an era name used during the reign of Emperor Taizong of the Song dynasty in imperial China.
-
B.
Yongli
Yongli was the era name of the last emperor of the Southern Ming dynasty, whose reign marked the final resistance of Ming loyalists against the Qing conquest in 17th-century China.
-
C.
Longqing
Longqing was the era name of a brief but notable period of the Ming dynasty in China, associated with the reign of the Longqing Emperor in the 16th century.
-
D.
Shàoyáng
Shàoyáng is a prefecture-level city in southwestern Hunan Province, China, known for its long history, diverse ethnic culture, and role as a regional transportation and commercial hub.
-
E.
Yongcheng
Yongcheng was a Qing dynasty imperial prince, known as one of the sons of the Qianlong Emperor of 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f4d9ddc8190a7dcf85ed47ee6c3 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde6f2bf388190ad3849317659756e |
completed | April 2, 2026, 3:48 a.m. |
Created at: March 30, 2026, 5:24 p.m.