Triple
T10002890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Hao |
E197369
|
entity |
| Predicate | capitalDuringReign |
P9119
|
FINISHED |
| Object | Jianye |
E190202
|
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: Jianye | Statement: [Sun Hao, capitalDuringReign, Jianye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jianye Context triple: [Sun Hao, capitalDuringReign, Jianye]
-
A.
Jianye
chosen
Jianye is an ancient name for the city now known as Nanjing, a historically significant capital in several Chinese dynasties.
-
B.
Yuncheng
Yuncheng is a major city in southern Shanxi Province, China, known for its historical sites and role as a regional transportation and economic hub.
-
C.
Licheng
Licheng is the courtesy name of the Daoguang Emperor, a Qing dynasty ruler of China in the early 19th century.
-
D.
Jianyang
Jianyang is a county-level city in northern Fujian Province, China, known for its historical role in tea production and its location along the Min River.
-
E.
Jingnan
Jingnan was a small regional kingdom in south-central China that existed during the Five Dynasties and Ten Kingdoms period.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcd12f6488190bd5257b5f65437cc |
completed | April 2, 2026, 1:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d30020305c81909c4fb01291c70cb6 |
completed | April 6, 2026, 12:36 a.m. |
Created at: March 30, 2026, 8:51 p.m.