Triple
T5690494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taishanese |
E125416
|
entity |
| Predicate | languageGroup |
P3349
|
FINISHED |
| Object | Yue |
E172883
|
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: Yue | Statement: [Taishanese, languageGroup, Yue]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yue Context triple: [Taishanese, languageGroup, Yue]
-
A.
Yue
chosen
Yue is a given name that appears in various East Asian cultures, often associated with meanings like "moon" or "delight" depending on the characters used.
-
B.
Tian
Tian is a Chinese given name commonly used for both males and females, often associated with meanings related to "sky" or "heaven."
-
C.
Qiyu
Qiyu was the personal name of the Jingtai Emperor, a 15th-century ruler of China's Ming dynasty.
-
D.
Hui
The Hui are a predominantly Muslim ethnic group in China known for their integration of Islamic faith with Han Chinese language and cultural practices.
-
E.
Luoyi
Luoyi was an ancient Chinese city that served as a major political and cultural center of the Zhou dynasty.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c023e340a08190b6175fad3e9a32b6 |
completed | March 22, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a47457c8190bc75f11a7f011a8a |
completed | March 22, 2026, 9:08 p.m. |
Created at: March 22, 2026, 3:44 p.m.