Triple
T10057209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Gaozu of Tang |
E208891
|
entity |
| Predicate | templeName |
P44027
|
FINISHED |
| Object | Gaozu |
E842785
|
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: Gaozu | Statement: [Emperor Gaozu of Tang, templeName, Gaozu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gaozu Context triple: [Emperor Gaozu of Tang, templeName, Gaozu]
-
A.
Gaozu
chosen
Gaozu was the temple name of Emperor Gaozu of Tang, the founder and first emperor of China’s Tang dynasty.
-
B.
Gaozu
Gaozu is the posthumous temple name honoring the influential Cao Wei statesman and strategist Sima Yi, later revered as a dynastic founder figure.
-
C.
Emperor Gaozu of Han
Emperor Gaozu of Han was the founder and first emperor of China’s Han dynasty, rising from peasant origins to unify the country after the collapse of the Qin.
-
D.
Emperor Wen
Emperor Wen is the posthumous imperial title of Cao Pi, the founding emperor of the state of Cao Wei during China’s Three Kingdoms period.
-
E.
Emperor Wen
Emperor Wen is the posthumous temple name honoring Emperor Taizong of the Song dynasty, reflecting his legacy as a key consolidator of early Song rule 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfaf7700819084dedf7b63e789c1 |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3697d5b008190b274a086172c7a7d |
completed | April 6, 2026, 8:06 a.m. |
Created at: March 30, 2026, 8:57 p.m.