Triple
T7998024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Taizu of Song |
E186175
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Kaibao |
E703880
|
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: Kaibao | Statement: [Emperor Taizu of Song, eraName, Kaibao]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaibao Context triple: [Emperor Taizu of Song, eraName, Kaibao]
-
A.
Kaibao
chosen
Kaibao was the era name marking the early reign of Emperor Taizu, founder of China’s Song dynasty.
-
B.
Qibao
Qibao is an ancient water town and popular tourist area in Shanghai, known for its historic streets, canals, and traditional architecture.
-
C.
Sanbao
Sanbao, better known in the West as Zheng He, was a famed 15th-century Chinese admiral and explorer who led the Ming dynasty’s great maritime expeditions across the Indian Ocean.
-
D.
Tianbao
Tianbao was an era name used during the Northern Qi dynasty in imperial China to designate a specific reign period.
-
E.
Majiabao
Majiabao is a neighborhood-level area located within Beijing’s Fengtai District, known primarily as a residential and commercial urban locality.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c98e39081908904d36a31bd6768 |
completed | March 31, 2026, 3:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc56910dd4819084ffe3350f15d95d |
completed | March 31, 2026, 11:19 p.m. |
Created at: March 30, 2026, 5:17 p.m.