Triple
T7302494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khasi people |
E167891
|
entity |
| Predicate | ethnicity |
P194
|
FINISHED |
| Object | Khasi |
E167891
|
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: Khasi | Statement: [Khasi people, ethnicity, Khasi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Khasi Context triple: [Khasi people, ethnicity, Khasi]
-
A.
Khasi language
Khasi language is an Austroasiatic language spoken primarily in the northeastern Indian state of Meghalaya by the Khasi people.
-
B.
Khasi people
chosen
The Khasi people are an indigenous ethnic group of the eastern Himalayas known for their matrilineal society, distinct Austroasiatic language, and rich cultural traditions centered in the hills of present-day Meghalaya.
-
C.
Dholuo
Dholuo is a Nilotic language spoken primarily by the Luo people of western Kenya and parts of Tanzania.
-
D.
Bhutia
Bhutia is a Sino-Tibetan language spoken primarily by the Bhutia community in the Himalayan regions of India, especially in Sikkim and parts of West Bengal.
-
E.
Burushaski
Burushaski is a language isolate spoken by the Burusho people in northern Pakistan, particularly in the Hunza, Nagar, and Yasin valleys of Gilgit-Baltistan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb2261c8190ae9095c8e110b528 |
completed | March 27, 2026, 8:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e558098c819091562566c59332e2 |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3:01 p.m.