Triple

T12061473
Position Surface form Disambiguated ID Type / Status
Subject Åström–Wittenmark adaptive control framework E287179 entity
Predicate typicalControllerType P103005 FINISHED
Object model reference adaptive controller LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: model reference adaptive controller | Statement: [Åström–Wittenmark adaptive control framework, typicalControllerType, model reference adaptive controller]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalControllerType
Context triple: [Åström–Wittenmark adaptive control framework, typicalControllerType, model reference adaptive controller]
  • A. typicalCoreType
    Indicates that something is a standard or characteristic core type within a given classification or system.
  • B. typicalComponent
    Indicates that one entity is a standard or representative component or part of another entity.
  • C. typeOfControl
    Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
  • D. controlsType
    Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
  • E. typicalEntryType
    Indicates the usual or standard category or kind of entry associated with something.
  • F. None of above. chosen

Provenance (4 batches)

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.
NER Named-entity recognition batch_69d9100b4ca8819084845ca4c13e34ce completed April 10, 2026, 2:58 p.m.
PD Predicate disambiguation batch_69d902bda47c8190b94860b31df4a98c completed April 10, 2026, 2:01 p.m.
PDg Predicate description generation batch_69d91006e14081909838412df082f794 completed April 10, 2026, 2:58 p.m.
Created at: April 8, 2026, 9:48 p.m.