Triple
T25371913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glushkov construction |
E632952
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | formal language theory concept |
C48921
|
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: formal language theory concept Context triple: [Glushkov construction, instanceOf, formal language theory concept]
-
A.
operation in formal language theory
chosen
An operation in formal language theory is a well-defined procedure, such as union, concatenation, or Kleene star, that takes one or more formal languages as input and produces another formal language as output.
-
B.
formal grammar notation
A formal grammar notation is a precise symbolic system for defining the syntactic structure of languages by specifying how valid strings can be generated from a set of production rules.
-
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.
hierarchy of formal grammars
A hierarchy of formal grammars is an organized classification of grammars into levels based on their generative power and structural constraints, such as the Chomsky hierarchy from regular to recursively enumerable languages.
-
E.
formal language specification
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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:38 p.m.