Triple
T22298037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deng |
E551174
|
entity |
| Predicate | hasVariantTransliteration |
P5923
|
FINISHED |
| Object | Teng (Wade–Giles) |
—
|
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: Teng (Wade–Giles) | Statement: [Deng, hasVariantTransliteration, Teng (Wade–Giles)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teng (Wade–Giles) Context triple: [Deng, hasVariantTransliteration, Teng (Wade–Giles)]
-
A.
Teng
chosen
Teng is a Chinese surname borne by various notable historical and contemporary figures in China.
-
B.
Tung-Yen
Tung-Yen is the Chinese given name of T.Y. Lin, the influential civil engineer renowned for his pioneering work in modern prestressed concrete design.
-
C.
Zeng
Zeng is a Chinese surname and given name commonly rendered in pinyin and borne by numerous historical and contemporary figures in China.
-
D.
Ting-Lu
Ting-Lu is a Dark/Ground-type legendary Pokémon from the Paldea region, known as one of the Treasures of Ruin associated with a cursed vessel.
-
E.
Teng Dai
Teng Dai is a person notable enough to be recognized as a prominent bearer of the Chinese surname Teng.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1572200c88190b9413286136fef15 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:41 p.m.