Triple
T36663729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB 1.0 |
E905201
|
entity |
| Predicate | supportsFullSpeed |
P31519
|
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, supportsFullSpeed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFullSpeed Context triple: [USB 1.0, supportsFullSpeed, true]
-
A.
supportsBusSpeed
chosen
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
B.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
C.
supportsVelocity
Indicates that one entity is capable of handling, providing, or being compatible with velocity-related data, behavior, or operations for another entity.
-
D.
requiresSpeed
Indicates that an entity needs to be performed, operated, or handled at or above a certain speed in order to be valid or effective.
-
E.
supportsIntelSpeedShift
Indicates that one entity provides compatibility with or enables the Intel Speed Shift power/performance management technology for another entity.
- 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.