Triple

T36663737
Position Surface form Disambiguated ID Type / Status
Subject USB 1.0 E905201 entity
Predicate supportsHotSwapping P10793 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: [USB 1.0, supportsHotSwapping, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsHotSwapping
Context triple: [USB 1.0, supportsHotSwapping, true]
  • A. hotSwappable
    Indicates that one component can be removed and replaced with another while the overall system remains powered on and operational.
  • B. supportsStreamingCompilation
    Indicates that an entity is capable of performing compilation in a streaming manner, processing and compiling input incrementally as it is received rather than requiring the entire input up front.
  • C. supportsIncrementalCompilation
    Indicates that the subject system or tool is capable of performing incremental compilation, recompiling only the parts of the codebase that have changed rather than rebuilding everything from scratch.
  • D. isHotPluggable chosen
    Indicates that a device or component can be connected to or disconnected from a system while it is powered on and operating, without requiring a shutdown or restart.
  • E. supportsDynamicInstrumentation
    Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
  • 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_69f76e6e3b908190970251b30f76ad71 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037c8e2c648190a65fc9c7872861af completed May 12, 2026, 7:16 p.m.
PD Predicate disambiguation batch_6a037a0e039481908a4a2666f76c5363 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:12 p.m.