Triple
T13299518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Tai |
E316769
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Wuming Zhuang |
E545686
|
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: Wuming Zhuang | Statement: [Central Tai, hasLanguage, Wuming Zhuang]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wuming Zhuang Context triple: [Central Tai, hasLanguage, Wuming Zhuang]
-
A.
Wuming Zhuang
chosen
Wuming Zhuang is a major variety of the Zhuang language spoken primarily in the Wuming District of Guangxi, China.
-
B.
Jingxi Zhuang
Jingxi Zhuang is a variety of the Zhuang language spoken in the Jingxi region of Guangxi, China, belonging to the Central Tai branch of the Tai–Kadai language family.
-
C.
Qiubei Zhuang
Qiubei Zhuang is a variety of the Zhuang language spoken by Zhuang communities in Qiubei County in southwestern China.
-
D.
Debao Zhuang
Debao Zhuang is a variety of the Zhuang language spoken in Debao County in Guangxi, China, belonging to the Central Tai branch of the Tai–Kadai language family.
-
E.
Fangzhuang
Fangzhuang is a residential neighborhood and commercial area in Beijing, China, known as one of the city’s earlier large-scale planned communities.
- 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d990a43ed88190a8dbbbd7d6d62dc4 |
completed | April 11, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7305fd57881909c1d7f09f3c084cf |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:28 p.m.