Triple
T36690997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barracuda Pro |
E905954
|
entity |
| Predicate | rotationalSpeed |
P99987
|
FINISHED |
| Object | 7200 RPM |
—
|
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: 7200 RPM | Statement: [Barracuda Pro, rotationalSpeed, 7200 RPM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotationalSpeed Context triple: [Barracuda Pro, rotationalSpeed, 7200 RPM]
-
A.
hasRotationalVelocityKmPerSec
Indicates that an entity possesses a rotational speed measured in kilometers per second.
-
B.
hasRotationalVelocity
Indicates that an entity is rotating and specifies the rate and direction of its angular motion around an axis.
-
C.
hasRotationFrequency
chosen
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
D.
rotorSpeedTypical
Indicates the usual or characteristic rotational speed associated with a rotor under normal or standard operating conditions.
-
E.
hasProjectedRotationalVelocity_kmPerS
Indicates the rotational speed an object appears to have along our line of sight, measured in kilometers per second.
- 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_69f76e70d2448190bdd3ce781ba971c5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7c767cc81909fbed9de6af09e55 |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.