Triple
T23408578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yixuan |
E560001
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Prince Chun |
E1171277
|
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 Chun | Statement: [Yixuan, title, Prince Chun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prince Chun Context triple: [Yixuan, title, Prince Chun]
-
A.
Prince Chun
chosen
Prince Chun was a Qing dynasty imperial prince and high-ranking noble closely connected to the ruling Aisin Gioro family.
-
B.
Prince Chui
Prince Chui was a royal prince of the Thonburi Kingdom and a son of King Taksin of Siam.
-
C.
Prince Tada
Prince Tada was a Japanese imperial prince of the Higashikuni-no-miya branch of the Imperial Family, noted as a member of this collateral royal house.
-
D.
Prince Uimin
Prince Uimin was a Korean royal prince of the Joseon dynasty and the Korean Empire, known as a younger son of Emperor Gojong and a key figure in the final years of Korea’s monarchy under Japanese rule.
-
E.
Prince Rong
Prince Rong is a Qing dynasty princely title historically associated with Yongqi, a son of the Qianlong Emperor.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50fff10819094e71fb0c11b7d95 |
completed | April 29, 2026, 6:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c67979c288190a5ef21c30ab4791d |
completed | May 19, 2026, 1:37 p.m. |
Created at: April 17, 2026, 5:38 p.m.