Triple
T9051060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chut |
E216882
|
entity |
| Predicate | hasLanguage |
P15
|
FINISHED |
| Object | Ruc language |
E615583
|
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: Ruc language | Statement: [Chut, hasLanguage, Ruc language]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruc language Context triple: [Chut, hasLanguage, Ruc language]
-
A.
Rục language
chosen
Rục language is a highly endangered Vietic language spoken by the small Rục ethnic group in the mountainous regions of central Vietnam.
-
B.
Rumsen language
Rumsen language is an extinct Ohlone (Costanoan) Native American language formerly spoken in the Monterey Bay area of California.
-
C.
Rarámuri language
The Rarámuri language is an indigenous Uto-Aztecan language spoken by the Tarahumara (Rarámuri) people of northern Mexico.
-
D.
Rade language
The Rade language is an Austronesian language spoken by the Rade (Êđê) people of Vietnam’s Central Highlands, notable for its Chamic roots and distinctive oral traditions.
-
E.
Lusei language
The Lusei language is a Kuki-Chin language of the Tibeto-Burman family spoken primarily by the Lusei (Mizo) people in northeastern India, especially in Mizoram.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b54423081908d9fd985109e336a |
completed | April 1, 2026, 12:48 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffdbd54848190ba79d873321f4fc9 |
completed | April 3, 2026, 5:49 p.m. |
Created at: March 30, 2026, 7:10 p.m.