Triple
T17006561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chen dynasty |
E412585
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Jiankang |
E170345
|
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: Jiankang | Statement: [Chen dynasty, capital, Jiankang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jiankang Context triple: [Chen dynasty, capital, Jiankang]
-
A.
Jiankang
chosen
Jiankang is the historical name of the Chinese city now known as Nanjing, which served as a major political and cultural center during several dynasties.
-
B.
Jingkang
Jingkang was the final era name of the Northern Song dynasty, marking the tumultuous period that culminated in the Jingkang Incident and the dynasty’s fall to the Jurchen Jin.
-
C.
Zhenjin
Zhenjin was the designated heir and favored son of Kublai Khan, known for his Confucian education and role in the early Yuan dynasty’s administration before his premature death.
-
D.
Jianchu
Jianchu was a named regnal era during the reign of Emperor Zhang of the Eastern Han dynasty in ancient China.
-
E.
Jiyuan
Jiyuan was a protected cruiser of the late 19th-century Beiyang Fleet of the Qing Dynasty, notable for its role in the First Sino-Japanese War.
- 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d3831268819089286053a5acf653 |
completed | April 18, 2026, 6:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc222d108190934ef2b3aa46aa22 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:32 a.m.