Triple
T15616088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony 3.5-inch floppy drive |
E375414
|
entity |
| Predicate | mediaWidth |
P19786
|
FINISHED |
| Object | 90 mm |
—
|
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: 90 mm | Statement: [Sony 3.5-inch floppy drive, mediaWidth, 90 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaWidth Context triple: [Sony 3.5-inch floppy drive, mediaWidth, 90 mm]
-
A.
mediaAspect
Indicates the specific aspect ratio or dimensional proportion of a media item in relation to its width and height.
-
B.
mediaCapacity
Indicates the maximum amount or volume of content that a given medium or storage resource can hold or handle.
-
C.
mediaDependentInterface
Indicates that one interface or interaction is contingent on, or varies according to, the characteristics or type of the media involved.
-
D.
mediaFeature
Indicates a characteristic, capability, or attribute of a media item that distinguishes how it is presented, functions, or is experienced.
-
E.
typicalWidth
chosen
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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.