Triple
T8006852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Quan |
E186382
|
entity |
| Predicate | capitalEstablished |
P1263
|
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 Quan, capitalEstablished, Jianye]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jianye Context triple: [Sun Quan, capitalEstablished, 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.
Liyang
Liyang is a county-level city in Jiangsu Province, China, known for its scenic attractions such as Tianmu Lake and its administration under the prefecture-level city of Changzhou.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf8a6048190970685a83fd2f59d |
completed | March 31, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd94574a9c8190b826438a51f9ca02 |
completed | April 1, 2026, 9:55 p.m. |
Created at: March 30, 2026, 5:18 p.m.