Triple

T36035050
Position Surface form Disambiguated ID Type / Status
Subject Guibei Zhuang E1042372 entity
Predicate closelyRelatedTo P37 FINISHED
Object Liujiang Zhuang
Liujiang Zhuang is a dialect of the Zhuang language spoken primarily in the Liujiang region of Guangxi, China, closely related to the Guibei Zhuang variety.
E2172911 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: Liujiang Zhuang | Statement: [Guibei Zhuang, closelyRelatedTo, Liujiang Zhuang]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Liujiang Zhuang
Triple: [Guibei Zhuang, closelyRelatedTo, Liujiang Zhuang]
Generated description
Liujiang Zhuang is a dialect of the Zhuang language spoken primarily in the Liujiang region of Guangxi, China, closely related to the Guibei Zhuang variety.

Provenance (5 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_69f76e2d7e8c8190bac4e90734566799 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7ad1a1be8819081dd0f9d41bf54a0 completed May 3, 2026, 8:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3933fc7328819088abb5cae079709a completed June 22, 2026, 1:09 p.m.
NEDg Description generation batch_6a39364d950c8190aad5d095a22d1c85 completed June 22, 2026, 1:19 p.m.
NED2 Entity disambiguation (via description) batch_6a3936b503448190b18cf2dc6bedd688 completed June 22, 2026, 1:20 p.m.
Created at: May 3, 2026, 4:07 p.m.