Triple
T17111507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsang |
E415236
|
entity |
| Predicate | romanizationOf |
P2508
|
FINISHED |
| Object | 曾 |
E89334
|
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: 曾 | Statement: [Tsang, romanizationOf, 曾]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 曾 Context triple: [Tsang, romanizationOf, 曾]
-
A.
陳
陳 is a common Chinese surname and character with historical roots, widely used across Chinese-speaking communities and often romanized as "Chan," "Chen," or similar variants.
-
B.
詹
詹 is a Chinese surname and character commonly romanized as "Chan" in Cantonese.
-
C.
鄭
鄭 is a common Korean family name of Chinese origin, typically romanized as Jeong, Jung, or Chung.
-
D.
Zeng
chosen
Zeng is a Chinese surname and given name commonly rendered in pinyin and borne by numerous historical and contemporary figures in China.
-
E.
苏
苏 is the standard Chinese abbreviation used to refer to Jiangsu Province in eastern 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc2a7f2c81908eb19594b6accab7 |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a014145f7988190803d5c5e4f2705b0 |
completed | May 11, 2026, 2:39 a.m. |
Created at: April 10, 2026, 5:35 a.m.