Triple
T13510696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenzhounese |
E321130
|
entity |
| Predicate | nativeName |
P15
|
FINISHED |
| Object | 温州话 |
E321130
|
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: [Wenzhounese, nativeName, 温州话]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 温州话 Context triple: [Wenzhounese, nativeName, 温州话]
-
A.
客家话
客家话是一种主要分布于中国南方及海外华人社区的汉语方言群，以其独特的语音、词汇和保留较多古汉语成分而著称。
-
B.
Wenzhounese
chosen
Wenzhounese is a highly distinctive and notoriously difficult-to-understand variety of Wu Chinese spoken in and around Wenzhou in southeastern Zhejiang province.
-
C.
Ningbo dialect
The Ningbo dialect is a variety of Wu Chinese spoken in and around the city of Ningbo in Zhejiang province, known for its distinct phonology and limited mutual intelligibility with Mandarin.
-
D.
Quanzhou dialect
The Quanzhou dialect is a major variety of Southern Min Chinese spoken in and around Quanzhou in Fujian, historically influential in the development of other Hokkien dialects.
-
E.
Zhangzhou dialect
The Zhangzhou dialect is a major Southern Min (Hokkien) variety from Zhangzhou in Fujian, influential in the formation of many overseas Chinese Hokkien dialects.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf86a6208190be8c18f7a0158f23 |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75490291c8190b5985d8c90ef1af6 |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:43 p.m.