Triple
T17445760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiande |
E424778
|
entity |
| Predicate | follows |
P134
|
FINISHED |
| Object | Wuping |
—
|
NE NERFINISHED |
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: Wuping | Statement: [Jiande, follows, Wuping]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wuping Context triple: [Jiande, follows, Wuping]
-
A.
Wuping
chosen
Wuping was an era name used during the Northern Qi dynasty in imperial China, marking a specific reign period within that dynasty’s rule.
-
B.
Xiping
Xiping was an era name used during the reign of Emperor Ling in the late Eastern Han dynasty of China.
-
C.
Maoping
Maoping is a historic village in China’s Jinggangshan region known as an early revolutionary stronghold and base area of the Chinese Red Army and Communist leadership.
-
D.
Lengshuikeng
Lengshuikeng is a geothermal area in Taiwan’s Yangmingshan National Park known for its hot springs, sulfur vents, and volcanic landscapes.
-
E.
Yongcong
Yongcong was a Qing dynasty imperial prince, one of the sons of the Qianlong Emperor of China.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffafec48190b25980318cea353f |
completed | April 19, 2026, 3:46 a.m. |
Created at: April 10, 2026, 5:47 a.m.