Triple
T15616083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony 3.5-inch floppy drive |
E375414
|
entity |
| Predicate | commonRotationSpeed |
P99987
|
FINISHED |
| Object | 300 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: 300 RPM | Statement: [Sony 3.5-inch floppy drive, commonRotationSpeed, 300 RPM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonRotationSpeed Context triple: [Sony 3.5-inch floppy drive, commonRotationSpeed, 300 RPM]
-
A.
hasRotationFrequency
chosen
Indicates that one entity possesses or is characterized by a specific rate at which it rotates over time.
-
B.
isRapidlyRotating
Indicates that an entity is spinning or rotating at a very high angular speed relative to a typical or reference rate.
-
C.
spinDownRate
Indicates the rate at which an object’s rotational speed decreases over time.
-
D.
rotatedMoreFrequentlyThan
Indicates that one entity undergoes rotation or is turned around its axis more often within a given time period than another entity.
-
E.
recommendedSpeed
Indicates the speed that is advised or suggested as appropriate under given conditions, rather than required or actual speed.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e980b748190b43c0b650bf1e629 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.