Triple
T14069617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tengwang Pavilion |
E338569
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Prince Teng |
E1078064
|
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 Teng | Statement: [Tengwang Pavilion, namedAfter, Prince Teng]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Prince Teng Context triple: [Tengwang Pavilion, namedAfter, Prince Teng]
-
A.
Prince Teng
chosen
Prince Teng was a Tang dynasty imperial prince best known for lending his name to the famed Tengwang Pavilion, one of China's most celebrated historic towers.
-
B.
Prince Chui
Prince Chui was a royal prince of the Thonburi Kingdom and a son of King Taksin of Siam.
-
C.
Prince Dan of Yan
Prince Dan of Yan was a royal prince of the ancient Chinese state of Yan, best known for orchestrating the failed assassination attempt on the Qin king by the assassin Jing Ke during the Warring States period.
-
D.
Prince of Jin
Prince of Jin was the princely title held by Zhao Guangyi before he ascended the throne as Emperor Taizong of the Song dynasty.
-
E.
Prince of Jin
The Prince of Jin was a noble title held by Li Zhi before he became Emperor Gaozong of the Tang dynasty in China.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568d0404819087e0fe37c72162cb |
completed | April 14, 2026, 3 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd09f69c08190b5cd12f9ff1a3f73 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:21 p.m.