Triple

T22719651
Position Surface form Disambiguated ID Type / Status
Subject Lilienfeld field-effect transistor concept E561825 entity
Predicate hasControlMechanism P8166 FINISHED
Object electric field 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: electric field | Statement: [Lilienfeld field-effect transistor concept, hasControlMechanism, electric field]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasControlMechanism
Context triple: [Lilienfeld field-effect transistor concept, hasControlMechanism, electric field]
  • A. hasMechanism chosen
    Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
  • B. hasTriggerMechanism
    Indicates that an entity possesses or is equipped with a specific mechanism used to initiate or activate an action or process.
  • C. hasMechanicalFeature
    Indicates that one entity possesses, includes, or is characterized by a specific mechanical component, attribute, or functionality.
  • D. requiresControlSystem
    Indicates that one entity depends on or mandates the presence of a control system associated with another entity in order to function or be valid.
  • E. hasPhysicalControl
    Indicates that one entity currently exercises direct, tangible control or possession over another entity or object.
  • F. None of above.

Provenance (3 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_69e2454fc984819088213b58ee87a002 completed April 17, 2026, 2:35 p.m.
NER Named-entity recognition batch_69f17910deb48190b38174e16868f3dd completed April 29, 2026, 3:20 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:19 p.m.