Triple
T38221894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transeurasian hypothesis |
E1012033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | language macrofamily proposal |
C64955
|
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: language macrofamily proposal Context triple: [Transeurasian hypothesis, instanceOf, language macrofamily proposal]
-
A.
language-family relationship proposal
chosen
A language-family relationship proposal is a scholarly hypothesis suggesting that two or more language families share a common genetic origin based on comparative linguistic evidence.
-
B.
language family
A language family is a group of languages that have evolved from a common ancestral language and share systematic similarities in vocabulary, grammar, and sound patterns.
-
C.
macro language
A macro language is a specialized scripting or command language used to automate repetitive tasks by recording, defining, and executing sequences of operations within a software environment.
-
D.
language family subgroup
A language family subgroup is a set of closely related languages within a larger language family that share a more recent common ancestor and distinctive linguistic features.
-
E.
macrolanguage variety
A macrolanguage variety is a specific linguistic form or set of forms that functions as one distinguishable member within a broader macrolanguage encompassing multiple closely related or mutually recognized language varieties.
- 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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.