Triple
T8186180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor Ling of Han |
E191188
|
entity |
| Predicate | eraNameIntroduced |
P2938
|
FINISHED |
| Object | Guanghe |
E744491
|
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: Guanghe | Statement: [Emperor Ling of Han, eraNameIntroduced, Guanghe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Guanghe Context triple: [Emperor Ling of Han, eraNameIntroduced, Guanghe]
-
A.
Guanghe
chosen
Guanghe was an era name used during the reign of Emperor Ling of the Eastern Han dynasty in ancient China.
-
B.
Guanggu
Guanggu is a major high-tech development zone in Wuhan, China, known as an innovation hub for the optics and electronics industries.
-
C.
Shàoyáng
Shàoyáng is a prefecture-level city in southwestern Hunan Province, China, known for its long history, diverse ethnic culture, and role as a regional transportation and commercial hub.
-
D.
Houyuan
Houyuan was a historical Chinese era name used during the reign of Emperor Jing of the Western Han dynasty.
-
E.
Dunhua
Dunhua is a county-level city in northeastern China's Jilin Province, known for its location within the Yanbian Korean Autonomous Prefecture and its mix of Han and Korean cultural influences.
- 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_69cebb1519048190bf3060a8c649cb9b |
completed | April 2, 2026, 6:53 p.m. |
Created at: March 30, 2026, 5:41 p.m.