Triple
T38678262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Cross branch |
E943816
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subgroup of Cross River languages |
C49616
|
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: subgroup of Cross River languages Context triple: [Lower Cross branch, instanceOf, subgroup of Cross River languages]
-
A.
subgroup of Niger–Congo languages
chosen
A subgroup of Niger–Congo languages is a set of closely related languages within the Niger–Congo family that share a common ancestral origin and distinctive structural and lexical features.
-
B.
Igbo subgroup
An Igbo subgroup is a distinct cultural, linguistic, and often geographically based division within the broader Igbo ethnic group, characterized by shared traditions, dialects, and social identities.
-
C.
subgroup of Cariban languages
A subgroup of Cariban languages is a set of closely related languages within the Cariban family that share common historical origins, structural features, and lexical similarities distinguishing them from other Cariban branches.
-
D.
Munda languages subgroup
The Munda languages subgroup is a branch of the Austroasiatic language family spoken primarily in eastern and central India, characterized by agglutinative morphology and distinctive phonological and syntactic features.
-
E.
Palaungic language subgroup
The Palaungic language subgroup is a branch of the Austroasiatic language family comprising several closely related languages spoken primarily by Palaung and related ethnic groups in Myanmar, China, Laos, and neighboring regions.
- 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.