Triple
T23094363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuki-Chin group |
E575842
|
entity |
| Predicate | hasMemberLanguage |
P7390
|
FINISHED |
| Object | Ralte language |
—
|
NE NERFINISHED |
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: Ralte language | Statement: [Kuki-Chin group, hasMemberLanguage, Ralte language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ralte language Context triple: [Kuki-Chin group, hasMemberLanguage, Ralte language]
-
A.
Ralte language
chosen
The Ralte language is a lesser-known Kuki-Chin language spoken by the Ralte people of northeastern India, primarily in the state of Mizoram.
-
B.
Ralte dialect
The Ralte dialect is a variety of the Falam Chin language spoken by the Ralte subgroup of the Chin people in parts of Myanmar and Northeast India.
-
C.
Raute language
Raute is a critically endangered Sino-Tibetan language spoken by the nomadic Raute people of Nepal.
-
D.
Olrat language
The Olrat language is an Oceanic language spoken by a small community in the Banks Islands of northern Vanuatu.
-
E.
Batuley language
The Batuley language is an Austronesian language spoken by a small community in Indonesia’s Aru Islands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de2ed088190971ff08c58b15aad |
completed | April 29, 2026, 4:49 a.m. |
Created at: April 17, 2026, 3:57 p.m.