Triple
T30369329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | transition network |
E772507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formalism in computational linguistics |
C18770
|
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: formalism in computational linguistics Context triple: [transition network, instanceOf, formalism in computational linguistics]
-
A.
framework in generative grammar
A framework in generative grammar is a theoretical system of principles and formal mechanisms used to model and explain the innate structure and rules underlying human language.
-
B.
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.
-
C.
formal language classification scheme
A formal language classification scheme is a systematic framework for categorizing formal languages based on their generative or recognitional power, typically using hierarchies such as the Chomsky hierarchy.
-
D.
knowledge representation formalism
A knowledge representation formalism is a structured, often mathematically grounded scheme for encoding information about the world so that it can be interpreted and manipulated by computational systems.
-
E.
formal language specification
chosen
A formal language specification is a precise, mathematically defined description of the syntax and structure of a language, typically using grammars and formal rules to unambiguously determine which strings belong to the language.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.