Triple
T8266598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luwic |
E193316
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of Anatolian languages |
C9203
|
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: branch of Anatolian languages Context triple: [Luwic, instanceOf, branch of Anatolian languages]
-
A.
branch of the Turkic languages
A branch of the Turkic languages is a subgroup of related Turkic languages that share a common historical origin, structural features, and vocabulary within the broader Turkic language family.
-
B.
Anatolian language
chosen
An Anatolian language is any member of an extinct branch of the Indo-European language family once spoken in ancient Anatolia (modern-day Turkey), including languages such as Hittite, Luwian, and Lycian.
-
C.
branch of Iranian languages
A branch of Iranian languages is a subgroup within the Iranian language family comprising closely related languages that share a common historical origin, structural features, and geographic distribution.
-
D.
Turkic language
A Turkic language is a member of a family of closely related languages spoken across a vast area from Eastern Europe and Anatolia through Central Asia to Siberia and Western China, characterized by agglutinative morphology, vowel harmony, and similar grammatical structures.
-
E.
branch of Semitic languages
A branch of Semitic languages is a subgroup within the Semitic language family comprising closely related languages that share common historical origins, structural features, and vocabulary.
- 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_69ca82e081d48190986beaa51f498ab9 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:50 p.m.