Triple
T28144813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurwitz determinants |
E714448
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | tool in control theory |
C21648
|
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: tool in control theory Context triple: [Hurwitz determinants, instanceOf, tool in control theory]
-
A.
control engineering concept
A control engineering concept is a theoretical or practical principle used to analyze, design, and optimize systems that automatically regulate their behavior to achieve desired performance.
-
B.
control theory conference
A control theory conference is a professional gathering where researchers, practitioners, and students present, discuss, and advance methods for analyzing and designing systems that regulate dynamic behavior.
-
C.
export control law
Export control law is the body of legal rules and regulations that govern the transfer of goods, technology, software, and services across national borders to protect national security, foreign policy interests, and international obligations.
-
D.
tool in signal processing
A tool in signal processing is a conceptual or physical mechanism—such as an algorithm, filter, transform, or software module—used to analyze, modify, or extract information from signals.
-
E.
tool in dynamical systems theory
chosen
A tool in dynamical systems theory is a conceptual or computational method—such as phase portraits, Lyapunov functions, or Poincaré maps—used to analyze, visualize, and understand the qualitative and quantitative behavior of dynamical systems over time.
- 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 27, 2026, 9:56 p.m.