Triple
T30861645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austroasiatic comparative linguistics |
E786076
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | comparative linguistics |
C48918
|
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: comparative linguistics Context triple: [Austroasiatic comparative linguistics, instanceOf, comparative linguistics]
-
A.
hypothesis in historical linguistics
A hypothesis in historical linguistics is a proposed explanation of how and why specific linguistic features or relationships between languages have changed over time, formulated to be tested against comparative and historical evidence.
-
B.
linguistics blog
A linguistics blog is an online platform that publishes accessible, often informal articles exploring language structure, use, history, and theory for both specialists and general readers.
-
C.
linguistic theory
Linguistic theory is the systematic study and modeling of the structure, use, and acquisition of language, aiming to explain how languages are organized, processed, and understood.
-
D.
tool in historical linguistics
chosen
A tool in historical linguistics is any methodological or analytical instrument—such as sound laws, comparative word lists, or phylogenetic models—used to reconstruct language histories, relationships, and changes over time.
-
E.
language contact
Language contact is the sociolinguistic phenomenon that occurs when speakers of different languages or dialects interact regularly, leading to mutual influence and change in their linguistic systems.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:47 p.m.