Triple
T9000286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WM-DD9 |
E215022
|
entity |
| Predicate | cassetteTypeSupported |
P85611
|
FINISHED |
| Object | Type I |
—
|
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: Type I | Statement: [Sony WM-DD9, cassetteTypeSupported, Type I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cassetteTypeSupported Context triple: [Sony WM-DD9, cassetteTypeSupported, Type I]
-
A.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
-
B.
opticalDiscType
Indicates the specific kind or category of an optical disc involved in the relationship (e.g., CD, DVD, Blu-ray).
-
C.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
D.
phonographicType
Indicates the specific kind or category of phonographic recording or medium associated with an entity.
-
E.
supportsPCM
Indicates that one entity is capable of handling, processing, or is compatible with PCM (Pulse-Code Modulation) audio data used by another entity.
- F. None of above. chosen
Provenance (4 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6954bb1881908d004a26ba7fe360 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edd6cb48190b4fc6d6ca0418056 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f6dec4081909379bd57c02a5710 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:05 p.m.