Triple
T30350715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-C310 |
E771980
|
entity |
| Predicate | hasVolumeControl |
P86392
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sony WI-C310, hasVolumeControl, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolumeControl Context triple: [Sony WI-C310, hasVolumeControl, yes]
-
A.
supportsVolumeControl
chosen
Indicates that one entity provides the capability to adjust or manage the audio volume level of another entity.
-
B.
hasVolumeElement
Indicates that something includes or is associated with a specific volumetric component or element within its structure or representation.
-
C.
hasSpeechLevels
Indicates that a language, dialect, or communicative system distinguishes different levels or styles of speech used according to social context, formality, or relative status between speakers.
-
D.
audioControlMethod
Indicates the method or mechanism by which audio playback or volume is controlled.
-
E.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 7:56 p.m.