Triple
T37186746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hainanese people |
E921340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Chinese ethnic subgroup |
C15841
|
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: Chinese ethnic subgroup Context triple: [Hainanese people, instanceOf, Chinese ethnic subgroup]
-
A.
ancient Chinese ethnic group
An ancient Chinese ethnic group is a historically distinct population within early Chinese civilization, characterized by shared ancestry, culture, language, and social practices documented in archaeological and textual records.
-
B.
Chin ethnic group
The Chin ethnic group is an indigenous community primarily inhabiting the Chin State of western Myanmar and neighboring regions, characterized by diverse sub-tribes, distinct Tibeto-Burman languages, and rich cultural traditions.
-
C.
ethnic group subcategory
chosen
An ethnic group subcategory is a more specific division within a broader ethnic group, distinguished by unique cultural, linguistic, historical, or regional characteristics.
-
D.
subgroup of the Yao people
A subgroup of the Yao people is a distinct cultural, linguistic, or regional division within the broader Yao ethnic community that shares core Yao heritage while maintaining its own specific traditions and social identity.
-
E.
subgroup of Yao people
A subgroup of Yao people is a distinct cultural, linguistic, or regional division within the broader Yao ethnic community, sharing core Yao heritage while maintaining its own specific traditions and social identity.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.