Triple
T12061442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Åström–Wittenmark adaptive control framework |
E287179
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | adaptive control methodology |
C22748
|
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: adaptive control methodology Context triple: [Åström–Wittenmark adaptive control framework, instanceOf, adaptive control methodology]
-
A.
adaptive learning rate method
An adaptive learning rate method is an optimization technique that automatically adjusts the step size for each parameter during training based on past gradient information to improve convergence speed and stability.
-
B.
adaptive suspension system
An adaptive suspension system is a vehicle suspension technology that continuously adjusts damping and stiffness in real time based on driving conditions, road surface, and driver inputs to optimize comfort, handling, and stability.
-
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.
control engineering concept
chosen
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.
-
E.
actor-critic method
An actor-critic method is a reinforcement learning approach that combines a policy model (actor) that selects actions with a value model (critic) that evaluates those actions to improve the policy.
- 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:48 p.m.