Triple
T21943231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangyun |
E541872
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Middle Chinese phonological source |
C29663
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Middle Chinese phonological source Context triple: [Guangyun, instanceOf, Middle Chinese phonological source]
-
A.
Chinese phonetic notation system
chosen
A Chinese phonetic notation system is a standardized set of symbols used to represent the pronunciation of Chinese characters, aiding in learning, reading, and accurate vocalization.
-
B.
Sinitic language
A Sinitic language is any member of the Chinese branch of the Sino-Tibetan language family, characterized by tonal phonology, analytic grammar, and a shared historical connection to Classical Chinese.
-
C.
Niger-Congo language reference system
A Niger-Congo language reference system is a structured framework for cataloging, describing, and cross-referencing the languages of the Niger-Congo family, including their classifications, features, and relationships.
-
D.
hypothesis in historical linguistics
A hypothesis in historical linguistics is a proposed explanation of how and why specific linguistic features or relationships between languages have changed over time, formulated to be tested against comparative and historical evidence.
-
E.
Sino-Tibetan language
A Sino-Tibetan language is any member of a large language family, including Chinese and Tibeto-Burman languages, characterized by shared historical origins in East and Southeast Asia and often featuring tonal systems and analytic grammar.
- F. None of above.
Provenance (1 batch)
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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 7:56 p.m.