Triple
T25534744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whispersync for Voice |
E640011
|
entity |
| Predicate | supportsModeSwitch |
P203
|
FINISHED |
| Object | text-to-audio |
—
|
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: text-to-audio | Statement: [Whispersync for Voice, supportsModeSwitch, text-to-audio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsModeSwitch Context triple: [Whispersync for Voice, supportsModeSwitch, text-to-audio]
-
A.
supportedMode
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
B.
supportsGraphicsSwitching
Indicates that an entity can dynamically switch between different graphics hardware or rendering modes, typically to balance performance and power usage.
-
C.
supportsMirrorMode
Indicates that one entity provides the capability for another entity or process to operate in a mirror or mirrored-display mode.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 21, 2026, 3:16 p.m.