Triple

T35689730
Position Surface form Disambiguated ID Type / Status
Subject Remote Control Unit E1031254 entity
Predicate ergonomicRequirement P183821 FINISHED
Object usable with limited dexterity 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: usable with limited dexterity | Statement: [Remote Control Unit, ergonomicRequirement, usable with limited dexterity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ergonomicRequirement
Context triple: [Remote Control Unit, ergonomicRequirement, usable with limited dexterity]
  • A. hasErgonomicType
    Indicates that an object or product is associated with a specific ergonomic classification or design type.
  • B. performanceRequirement
    Indicates that one entity specifies or imposes a required level of performance that another entity must meet or satisfy.
  • C. designedToMeetRequirement
    Indicates that something has been intentionally created or configured in order to satisfy a specified requirement.
  • D. structuralRequirement
    Indicates that one entity imposes or specifies necessary structural conditions or constraints that another entity must satisfy.
  • E. safetyRequirement
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • 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_69f76e0c73ec819080ab60a9e2f5f1f6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a34f8ee08190a040304635539a8f completed May 3, 2026, 7:34 p.m.
PD Predicate disambiguation batch_69f7a06f125c8190843af194f042a465 completed May 3, 2026, 7:22 p.m.
PDg Predicate description generation batch_69f7a34e80dc8190980d5b7b0b91341d completed May 3, 2026, 7:34 p.m.
Created at: May 3, 2026, 4:05 p.m.