Triple
T16600497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic |
E403317
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | branch of the Indo-European language family |
C7357
|
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 the Indo-European language family Context triple: [Italic, instanceOf, branch of the Indo-European language family]
-
A.
Indo-European language branch
chosen
The Indo-European language branch is a major subgroup within the Indo-European language family comprising closely related languages that share a common ancestral origin and distinctive linguistic features.
-
B.
Indo-European language
An Indo-European language is a member of a large family of related languages spoken across Europe and parts of Asia, all descended from a common prehistoric ancestor known as Proto-Indo-European.
-
C.
branch of the Germanic languages
A branch of the Germanic languages is a subgroup of related Germanic languages that share a common historical origin, structural features, and vocabulary, such as the North, West, or (extinct) East Germanic branches.
-
D.
branch of the Dravidian language family
A branch of the Dravidian language family is a subgroup of related Dravidian languages that share a common historical origin, structural features, and linguistic innovations distinguishing them from other Dravidian subgroups.
-
E.
Afroasiatic language branch
The Afroasiatic language branch is a major language family originating in the Middle East and North Africa, encompassing diverse languages such as Arabic, Hebrew, Amharic, and Hausa that share common historical and structural features.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.