Triple
T26201315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khosti Attan |
E655237
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional variation of Attan |
C32838
|
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: regional variation of Attan Context triple: [Khosti Attan, instanceOf, regional variation of Attan]
-
A.
regional variety of Toraja-Saʼdan
A regional variety of Toraja-Saʼdan is a geographically distinct form of the Toraja-Saʼdan language characterized by unique phonological, lexical, and grammatical features specific to a particular area or community.
-
B.
regional variety of Ghomalaʼ
A regional variety of Ghomalaʼ is a geographically localized dialect of the Ghomalaʼ language characterized by distinct phonological, lexical, or syntactic features specific to a particular area or community.
-
C.
regional variant of Arirang
A regional variant of Arirang is a localized version of the traditional Korean folk song whose melody, lyrics, and performance style have been adapted to reflect the distinct cultural, linguistic, and historical characteristics of a specific area.
-
D.
regional folk tradition
chosen
A regional folk tradition is a set of locally rooted customs, stories, practices, and expressions passed down through generations that reflect the shared history, values, and identity of a specific geographic community.
-
E.
Isnag dialect
The Isnag dialect is a variant of the Isnag language spoken by the Isnag people of northern Luzon in the Philippines, characterized by its distinct phonology, vocabulary, and grammatical features within the Northern Luzon language group.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
Created at: April 26, 2026, 8:48 p.m.