Triple
T6219920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manggala |
E139083
|
entity |
| Predicate | nobleTitle |
P914
|
FINISHED |
| Object | Prince of Anxi |
E580472
|
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: Prince of Anxi | Statement: [Manggala, nobleTitle, Prince of Anxi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prince of Anxi Context triple: [Manggala, nobleTitle, Prince of Anxi]
-
A.
Prince of Anxi
chosen
Prince of Anxi was a Yuan dynasty princely title associated with the Mongol imperial family, notably held by Manggala, a son of Kublai Khan.
-
B.
Prince of Yan
Prince of Yan was the noble title held by Zhu Di before he became the Yongle Emperor of the Ming dynasty.
-
C.
Prince of Cheng
The Prince of Cheng was a noble title in the Ming dynasty Chinese imperial hierarchy, held by Zhu Qiyu before he ascended the throne as the Jingtai Emperor.
-
D.
Prince of Xing
The Prince of Xing was the noble title held by the future Jiajing Emperor of the Ming dynasty before he ascended the throne of China.
-
E.
Emperor of the East
The Emperor of the East was the ruler of the Eastern Roman Empire, governing its territories, military, and administration from Constantinople during the late Roman imperial period.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bbb768819099402d367f124639 |
completed | March 22, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5190757648190a73575e680a35684 |
completed | March 26, 2026, 11:31 a.m. |
Created at: March 22, 2026, 4:21 p.m.