Triple
T21171301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wang Yangming |
E521696
|
entity |
| Predicate | courtesyName |
P570
|
FINISHED |
| Object | Bo'an |
—
|
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: Bo'an | Statement: [Wang Yangming, courtesyName, Bo'an]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bo'an Context triple: [Wang Yangming, courtesyName, Bo'an]
-
A.
Bo'an
chosen
Bo'an is the courtesy name of Wang Yangming, the influential Ming dynasty philosopher, statesman, and Neo-Confucian thinker.
-
B.
Xin'an
Xin'an is the historical name of the region now known as Huizhou in Guangdong, China, reflecting its earlier administrative and cultural identity.
-
C.
Xin’an
Xin’an is the former name of Nantou, a historic town in Shenzhen, China, that once served as an important administrative and commercial center in the region.
-
D.
Yongcong
Yongcong was a Qing dynasty imperial prince, one of the sons of the Qianlong Emperor of China.
-
E.
Jianning
Jianning was an era name used during the reign of Emperor Ling of the Eastern Han dynasty in ancient 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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7271351f08190b609a6c280c9a02a |
completed | April 21, 2026, 7:28 a.m. |
Created at: April 16, 2026, 3 p.m.