Triple
T4162737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northeast Caucasian languages |
E91568
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Budukh language |
E259674
|
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: Budukh language | Statement: [Northeast Caucasian languages, hasMember, Budukh language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Budukh language Context triple: [Northeast Caucasian languages, hasMember, Budukh language]
-
A.
Budong-Budong language
The Budong-Budong language is an Austronesian language spoken by a small community in West Sulawesi, Indonesia.
-
B.
Tsakhur language
chosen
The Tsakhur language is a Northeast Caucasian language spoken primarily by the Tsakhur people in parts of Azerbaijan and Dagestan.
-
C.
Udege language
The Udege language is a critically endangered Tungusic language spoken by the Udege people of the Russian Far East.
-
D.
Buga language
The Buga language is a lesser-known member of the Khoe family of southern African languages, spoken by a small community and considered endangered.
-
E.
Boro language
Boro language is a Tibeto-Burman language spoken primarily by the Boro people of Assam in northeastern India.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02a811608190aff8b663498711e8 |
completed | March 9, 2026, 5:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b57f456bf88190b9b8678476ac3803 |
completed | March 14, 2026, 3:31 p.m. |
Created at: March 9, 2026, 3:44 p.m.