Triple
T14639269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valyrian languages |
E343681
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | languages of A Song of Ice and Fire |
C35168
|
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: languages of A Song of Ice and Fire Context triple: [Valyrian languages, instanceOf, languages of A Song of Ice and Fire]
-
A.
language of Middle-earth
The language of Middle-earth is a richly constructed set of tongues, scripts, and linguistic histories created by J.R.R. Tolkien to give depth, culture, and realism to the peoples and stories of his fictional world.
-
B.
organization in A Song of Ice and Fire
An organization in A Song of Ice and Fire is a structured group of individuals—such as noble houses, religious orders, military factions, or secret societies—united by shared goals, loyalties, and rules that influence political, social, and military dynamics in Westeros and beyond.
-
C.
Algic language
An Algic language is any member of a family of Indigenous languages of North America, including the Algonquian branch and a few related languages, that share common ancestral linguistic features.
-
D.
Zenati language
The Zenati language is a conceptual class representing a branch of Berber languages characterized by shared phonological, morphological, and lexical features that distinguish it from other Afroasiatic language groups.
-
E.
Mon language
Mon language is an Austroasiatic language historically spoken by the Mon people of Myanmar and Thailand, notable for its ancient inscriptions and significant influence on the region’s scripts and cultures.
- F. None of above. chosen
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.