Triple
T8186182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ling of Han |
E191188
|
entity |
| Predicate | eraNameIntroduced |
P2938
|
FINISHED |
| Object | Jianning |
E748180
|
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: Jianning | Statement: [Emperor Ling of Han, eraNameIntroduced, Jianning]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jianning Context triple: [Emperor Ling of Han, eraNameIntroduced, Jianning]
-
A.
Jianning
chosen
Jianning was an era name used during the reign of Emperor Ling of the Eastern Han dynasty in ancient China.
-
B.
Longyan
Longyan is a prefecture-level city in western Fujian Province, China, known for its Hakka culture, mountainous landscapes, and historic tulou earthen dwellings.
-
C.
Bo'an
Bo'an is the courtesy name of Wang Yangming, the influential Ming dynasty philosopher, statesman, and Neo-Confucian thinker.
-
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.
Jinyang
Jinyang is the historical name of the city now known as Taiyuan, a major urban and industrial center in northern China’s Shanxi province.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb7266bc148190984060b7b95effb5 |
completed | March 31, 2026, 7:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf421875f88190a005c3ffba04dffe |
completed | April 3, 2026, 4:29 a.m. |
Created at: March 30, 2026, 5:41 p.m.