Triple
T14615201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buyantu Khan |
E343065
|
entity |
| Predicate | eraName |
P2938
|
FINISHED |
| Object | Yanyou |
E346249
|
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: Yanyou | Statement: [Buyantu Khan, eraName, Yanyou]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yanyou Context triple: [Buyantu Khan, eraName, Yanyou]
-
A.
Yanyou
chosen
Yanyou was a reign era of the Yuan dynasty under Emperor Ayurbarwada Buyantu Khan in the early 14th century.
-
B.
Jianyan
Jianyan was the reign era name marking the early rule of Emperor Gaozong during the Southern Song dynasty in China.
-
C.
Yanshou
Yanshou was a prominent 10th-century Chinese Chan (Zen) Buddhist monk and scholar known for synthesizing various Buddhist traditions and emphasizing the unity of different paths to enlightenment.
-
D.
Xingyuan
Xingyuan was the Chinese era name used during part of Emperor Dezong of Tang’s reign in the late eighth century.
-
E.
Laiyuan
Laiyuan was a late 19th-century Chinese armored cruiser of the Beiyang Fleet that fought in the First Sino-Japanese War.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb45264988190a1df13e8b54a85bd |
completed | April 14, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5cbcf08819084313bf28f0bb3e1 |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:25 a.m.