Triple
T20685391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meno-Mene |
E508399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sasak language variety |
C22569
|
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: Sasak language variety Context triple: [Meno-Mene, instanceOf, Sasak language variety]
-
A.
regional variety of the Sasak language
chosen
A regional variety of the Sasak language is a geographically and socially distinct form of Sasak characterized by systematic differences in pronunciation, vocabulary, and grammar from other Sasak varieties.
-
B.
Sambal language variety
Sambal language variety is a specific form or dialect of the Sambal language, characterized by distinct phonological, lexical, and grammatical features used by a particular Sambal-speaking community.
-
C.
Yana language variety
Yana language variety refers to any of the related but distinct forms of the Yana language traditionally spoken by the Yana people of northern California, encompassing dialectal differences in phonology, vocabulary, and grammar.
-
D.
Sabaic language variety
A Sabaic language variety is a specific form or dialect of the ancient South Arabian Sabaic language, distinguished by its unique linguistic features, geographic distribution, and historical context within the Sabaean cultural sphere.
-
E.
Nicobarese language variety
A Nicobarese language variety is a specific linguistic form or dialect within the Nicobarese branch of the Austroasiatic language family, spoken by the indigenous Nicobarese people of India’s Nicobar Islands.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 11:45 a.m.