Triple

T35662587
Position Surface form Disambiguated ID Type / Status
Subject LM101 operational amplifier E1030475 entity
Predicate hasOverloadProtection P183587 FINISHED
Object true 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: true | Statement: [LM101 operational amplifier, hasOverloadProtection, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOverloadProtection
Context triple: [LM101 operational amplifier, hasOverloadProtection, true]
  • A. hasOverload
    Indicates that an entity defines multiple variants (overloads) of the same operation or function, typically distinguished by differing parameters or signatures.
  • B. isOverprotectedBy
    Indicates that one entity receives an excessive or overly controlling level of protection from another entity.
  • C. hasOutputShortCircuitProtection
    Indicates that an entity provides or is equipped with protection against short circuits occurring at its output.
  • D. hasOverheadType
    Indicates that one entity is associated with a specific category or type of overhead (such as cost, resource, or operational overhead) that applies to it.
  • E. hasSlopeProtection
    Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
  • 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_69f76e09f87881909c954aaac176c34f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a01efcc08190bba489a9099b8684 completed May 3, 2026, 7:21 p.m.
PD Predicate disambiguation batch_69f79e4d885881908a3612e2e75cf84f completed May 3, 2026, 7:13 p.m.
PDg Predicate description generation batch_69f79f477c4c8190a35cb6d87b1dcbd1 completed May 3, 2026, 7:17 p.m.
Created at: May 3, 2026, 4:05 p.m.